Blimp Settings framework on the c++ side

chrome/browser/DEPS

Index: chrome/browser/DEPS
diff --git a/chrome/browser/DEPS b/chrome/browser/DEPS
index da930989e480b447e81b6de1aef6cb4af6dfacce..6d61bf76a839c6ad580f7940a3fe611528dbdc71 100644
--- a/chrome/browser/DEPS
+++ b/chrome/browser/DEPS
@@ -1,6 +1,7 @@
 include_rules = [
   "+apps",
   "+ash",
+  "+blimp/client/public",

[Lei Zhang, 2016/09/30 23:55:35]

If the Android-only portion of chrome::RegisterLocalState() moved into
chrome/browser/android, do you think this can be omitted, since
chrome/browser/android/DEPS already has this rule?

i.e. Do for foresee any other part of chrome/browser outside of
chrome/browser/android that will need to access blimp/client/public? 

[Menglin, 2016/10/01 00:08:31]

I know you meant RegisterProfilePrefs() :)

For now I can't think of any other part of chrome/browser needs access to
blimp/client/public. David, wdyt?

[David Trainor- moved to gerrit, 2016/10/01 03:26:35]

I'm fine with relying on the DEPS from chrome/browser/android :).  If we really
need to access blimp/client/public in chrome/browser in the future we can add a
DEPS then.

[Lei Zhang, 2016/10/03 23:13:54]

So do we want to refactor the Android-only portion of RegisterLocalState() and
RegisterProfilePrefs() into, say,
chrome/browser/android/preferences/browser_prefs.cc?

   "+chrome/app",
   "+chrome/chrome_watcher",
   "+chrome/grit",