OAuth2 support for Webstore downloads.

extensions/browser/DEPS

Index: extensions/browser/DEPS
diff --git a/extensions/browser/DEPS b/extensions/browser/DEPS
index 9b4dd6f798d3ee50123c60fcdfcc31e314311956..072f0ae9edcbcc2b4e4ca84db90d2a345c71aa87 100644
--- a/extensions/browser/DEPS
+++ b/extensions/browser/DEPS
@@ -2,6 +2,7 @@ include_rules = [
   "+components/keyed_service",
   "+components/pref_registry",
   "+content/public/browser",
+  "+google_apis/gaia",

[asargent_no_longer_on_chrome, 2014/08/06 00:26:29]

are you sure we want to take a dependency on this, instead of defining some
abstract interface that gets wired up inside chrome/browser/extensions/ ? 

[Ken Rockot(use gerrit already), 2014/08/06 16:49:55]

Even if I abstract away this dependency now, a time will soon come when we want
device identity support in app_shell, and that's going to end up depending on
gaia as well. So there's going to be a gaia-dependent component shared between
//extensions/shell and //chrome. It could live in its own //components
component, or maybe in a new //google_apis/webstore, but it will still depend on
gaia.

Alternatively, I don't see why OAuth2TokenService and/or IdentityProvider
themselves couldn't be abstracted away from google_apis into something more
generic like //components/oauth2. Then I would feel less bad about duplicating
specific google_apis dependencies within each extensions embedder rather than in
general-purpose extensions code.

+rogerta as OWNER of //google_apis/gaia - Any thoughts on this?

[asargent_no_longer_on_chrome, 2014/08/06 19:38:47]

BTW I'm not strongly opposed to the way you have it or anything - I just wanted
to make sure we thought it through before moving forward. 

   "+grit/extensions_strings.h",
   "+net",
   "+skia/ext/image_operations.h",