Add module for counting date-last-roll-call and persisting those counts

chrome/browser/component_updater/chrome_component_updater_configurator.cc

Index: chrome/browser/component_updater/chrome_component_updater_configurator.cc
diff --git a/chrome/browser/component_updater/chrome_component_updater_configurator.cc b/chrome/browser/component_updater/chrome_component_updater_configurator.cc
index 97e99e71a3045c27056573ceeca06d0449e41e9f..3850158b717d9efd837b942e44f596966b3eb109 100644
--- a/chrome/browser/component_updater/chrome_component_updater_configurator.cc
+++ b/chrome/browser/component_updater/chrome_component_updater_configurator.cc
@@ -7,6 +7,8 @@
 #include <string>
 #include <vector>
 
+#include "base/files/file_path.h"
+#include "base/path_service.h"
 #include "base/strings/sys_string_conversions.h"
 #include "base/threading/sequenced_worker_pool.h"
 #include "base/version.h"
@@ -17,6 +19,7 @@
 #include "chrome/browser/google/google_brand.h"
 #include "chrome/browser/update_client/chrome_update_query_params_delegate.h"
 #include "chrome/common/channel_info.h"
+#include "chrome/common/chrome_paths.h"
 #if defined(OS_WIN)
 #include "chrome/installer/util/google_update_settings.h"
 #endif
@@ -55,6 +58,7 @@ class ChromeConfigurator : public update_client::Configurator {
   bool UseCupSigning() const override;
   scoped_refptr<base::SequencedTaskRunner> GetSequencedTaskRunner()
       const override;
+  base::FilePath GetMetadataPath() const override;
 
  private:
   friend class base::RefCountedThreadSafe<ChromeConfigurator>;
@@ -172,6 +176,12 @@ ChromeConfigurator::GetSequencedTaskRunner() const {
           base::SequencedWorkerPool::CONTINUE_ON_SHUTDOWN);
 }
 
+base::FilePath ChromeConfigurator::GetMetadataPath() const {
+  base::FilePath result;
+  CHECK(PathService::Get(chrome::DIR_USER_DATA, &result));

[Sorin Jianu, 2016/04/07 04:03:19]

Do we need to CHECK? Can we be fault tolerant? I don't have an opinion, I am
just asking the question.

[waffles, 2016/04/07 17:04:43]

Done. In practice it won't matter because several component installers do this
same CHECK, but you make a good point.

+  return result.AppendASCII("component_metadata.json");
+}
+
 }  // namespace
 
 scoped_refptr<update_client::Configurator>