Split browser-specific and generic code in components/task_scheduler_util/.

components/task_scheduler_util/common/BUILD.gn

Index: components/task_scheduler_util/common/BUILD.gn
diff --git a/components/task_scheduler_util/initialization/BUILD.gn b/components/task_scheduler_util/common/BUILD.gn
similarity index 71%
rename from components/task_scheduler_util/initialization/BUILD.gn
rename to components/task_scheduler_util/common/BUILD.gn
index 213326bd9971e542f3c4bc0ada1d05f3f8d4d3a3..d0e0566f16c8857b815139686e7a85adf6e20b8f 100644
--- a/components/task_scheduler_util/initialization/BUILD.gn
+++ b/components/task_scheduler_util/common/BUILD.gn
@@ -2,10 +2,10 @@
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
-static_library("initialization") {
+static_library("common") {

[robliao, 2016/12/14 20:46:48]

Is the variations->common directory change necessary? The only thing in these
files are relevant to variations.

[fdoray, 2016/12/14 21:03:12]

Makes it clear that this will be used in browser and renderer processes
https://codereview.chromium.org/2568793003/. This is a "common" pattern in
components/
https://cs.chromium.org/search/?q=file:components/.*/common&sq=package:chromi...
Also, the whole component is related to variations, so it might not be clear
what goes in a variations/ subdirectory.

If you have strong feelings, I could keep variations/.

   sources = [
-    "browser_util.cc",
-    "browser_util.h",
+    "variations_util.cc",
+    "variations_util.h",
   ]
 
   deps = [
@@ -16,10 +16,10 @@ static_library("initialization") {
 source_set("unit_tests") {
   testonly = true
   sources = [
-    "browser_util_unittest.cc",
+    "variations_util_unittest.cc",
   ]
   deps = [
-    ":initialization",
+    ":common",
     "//base",
     "//testing/gtest",
   ]