Add a new "Configure" mechanism to CLD browser-side data interfaces.

chrome/browser/component_updater/cld_component_installer.h

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef CHROME_BROWSER_COMPONENT_UPDATER_CLD_COMPONENT_INSTALLER_H_
 #define CHROME_BROWSER_COMPONENT_UPDATER_CLD_COMPONENT_INSTALLER_H_
 
 #include <string>
 #include <vector>
 
@@ skipping 42 matching lines @@
   virtual std::string GetName() const OVERRIDE;
 
   static base::FilePath GetInstalledPath(const base::FilePath& base);
 
   // Sets the path to the CLD data file. Called internally once a valid CLD
   // data file has been observed. The implementation of this method is
   // responsible for configuring the CLD data source.
   // This method is threadsafe.
   static void SetLatestCldDataFile(const base::FilePath& path);
 
+  // Allows testing code to detect the file path that was ultimately set in

[Sorin Jianu, 2014/07/29 17:56:56]

Can this code be for production, in other words, why do we have to special case
it for test only? In there an issue with exposing an accessor for the latest
data file?

[Andrew Hayden (chromium.org), 2014/07/29 19:51:55]

There is no issue, but there is also no need. It's a one-way thing, you set it
and forget it. The only thing that would need this info is that code in
components/translate, which by definition should not have dependencies on THIS
code.

If we do have a need for it, I'm happy to remove the _ForTest suffix.

+  // SetLatestCldDataFile.
+  static base::FilePath GetLatestCldDataFile_ForTest();
+
   DISALLOW_COPY_AND_ASSIGN(CldComponentInstallerTraits);
 };
 
 // Call once during startup to make the component update service aware of
 // the CLD component.
 void RegisterCldComponent(ComponentUpdateService* cus);
 
 }  // namespace component_updater
 
 #endif  // CHROME_BROWSER_COMPONENT_UPDATER_CLD_COMPONENT_INSTALLER_H_