Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(9070)

Unified Diff: chrome/browser/api/DEPS

Issue 14188052: Remove now-unused c/b/api/ directory. (Closed) Base URL: svn://chrome-svn/chrome/trunk/src/
Patch Set: Created 7 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | chrome/browser/api/OWNERS » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: chrome/browser/api/DEPS
===================================================================
--- chrome/browser/api/DEPS (revision 195279)
+++ chrome/browser/api/DEPS (working copy)
@@ -1,29 +0,0 @@
-# The chrome/browser/api directory is for programming interfaces
-# provided by Chrome to Browser Components that run within Chrome.
-# Files here are not allowed to include stuff under chrome/browser
-# since that would leak implementation details to users of the APIs.
-#
-# APIs can be either pure-virtual to allow specialization at runtime,
-# or they can be non-virtual and specialized per platform (or
-# otherwise at compile time), or a mix of non-virtual and virtual.
-# The primary initial objective is to break Browser Components'
-# dependencies on implementation details, so non-virtual classes in
-# header files that do not expose any headers from chrome/browser
-# except for chrome/browser/api are acceptable.
-#
-# Note that for non-virtual APIs, there is an increased risk of an
-# implicit link-time dependency remaining from the user of the API to
-# the implementation. We are accepting this risk initially, but plan
-# to write a new type of link-time or target-level set of dependency
-# rules to help us find such problems and reduce them over time.
-#
-# The directory structure under chrome/browser/api/ is a mirror of
-# those parts of the chrome/browser/ structure that APIs have been
-# extracted from. Hence, an API defined in chrome/browser/api/x/y/z
-# is likely to be implemented in a directory chrome/browser/x/y/z.
-#
-# See http://www.chromium.org/developers/design-documents/browser-components
-include_rules = [
- "-chrome/browser",
- "+chrome/browser/api",
-]
« no previous file with comments | « no previous file | chrome/browser/api/OWNERS » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698