tree: 515a776b1d12815c47c6f8e48e91615c371bff87 [path history] [tgz]
  1. app/
  2. device_management/
  3. docs/
  4. linux/
  5. mac/
  6. policy/
  7. protos/
  8. test/
  9. tools/
  10. win/
  11. .style.yapf
  12. action_handler.h
  13. activity.cc
  14. activity.h
  15. activity_impl.h
  16. activity_impl_linux.cc
  17. activity_impl_mac.cc
  18. activity_impl_win.cc
  19. activity_impl_win_unittest.cc
  20. branding.gni
  21. BUILD.gn
  22. check_for_updates_task.cc
  23. check_for_updates_task.h
  24. COMMON_METADATA
  25. configurator.cc
  26. configurator.h
  27. constants.cc
  28. constants.h
  29. constants_prod.cc
  30. constants_test.cc
  31. crash_client.cc
  32. crash_client.h
  33. crash_reporter.cc
  34. crash_reporter.h
  35. crx_downloader_factory.h
  36. DEPS
  37. DIR_METADATA
  38. enum_traits.h
  39. enum_traits_unittest.cc
  40. external_constants.cc
  41. external_constants.h
  42. external_constants_builder.cc
  43. external_constants_builder.h
  44. external_constants_builder_unittest.cc
  45. external_constants_default.cc
  46. external_constants_default.h
  47. external_constants_override.cc
  48. external_constants_override.h
  49. external_constants_override_unittest.cc
  50. external_constants_prod.cc
  51. installer.cc
  52. installer.h
  53. installer_mac.cc
  54. launchd_util.cc
  55. launchd_util.h
  56. lib_util.cc
  57. lib_util.h
  58. lib_util_mac.mm
  59. lib_util_unittest.cc
  60. lib_util_win.cc
  61. OWNERS
  62. persisted_data.cc
  63. persisted_data.h
  64. persisted_data_unittest.cc
  65. prefs.cc
  66. prefs.h
  67. prefs_impl.h
  68. prefs_linux.cc
  69. prefs_mac.mm
  70. prefs_unittest.cc
  71. prefs_win.cc
  72. README.md
  73. registration_data.cc
  74. registration_data.h
  75. run_all_unittests.cc
  76. service_proxy_factory.h
  77. setup.h
  78. setup_linux.cc
  79. setup_mac.mm
  80. setup_win.cc
  81. splash_screen.h
  82. tag.cc
  83. tag.h
  84. tag_unittest.cc
  85. test_scope.h
  86. test_scope_system.cc
  87. test_scope_user.cc
  88. unittest_util.cc
  89. unittest_util.h
  90. unittest_util_unittest.cc
  91. update_block_check.cc
  92. update_block_check.h
  93. update_block_check_win.cc
  94. update_service.cc
  95. update_service.h
  96. update_service_impl.cc
  97. update_service_impl.h
  98. update_service_impl_inactive.cc
  99. update_service_impl_inactive.h
  100. update_service_internal.h
  101. update_service_internal_impl.cc
  102. update_service_internal_impl.h
  103. update_service_internal_impl_inactive.cc
  104. update_service_internal_impl_inactive.h
  105. update_service_internal_impl_qualifying.cc
  106. update_service_internal_impl_qualifying.h
  107. update_service_unittest.cc
  108. updater.cc
  109. updater.h
  110. updater_branding.h.in
  111. updater_scope.cc
  112. updater_scope.h
  113. updater_scope_unittest.cc
  114. updater_unittest.cc
  115. updater_version.h.in
  116. util.cc
  117. util.h
  118. util_mac.mm
  119. util_mac_unittest.mm
  120. util_win.cc
chrome/updater/README.md

An updater for desktop client software using Chromium code and tools.

The updater will be built from a common, platform neutral code base, as part of the Chrome build. The updater is going to be a drop-in replacement for Google Update/Omaha/Keystone and could be customized by 3rd party embedders to for updating non-Google client software, such as Edge.

The desktop platforms include Windows, macOS, Linux.

There are many reasons to start a new code base for this:

  • Reducing the development cost and the code duplication among platforms.
  • Implementing update algorithms consistently and correctly: checking for updates, applying updates, gathering metrics, and load shedding.
  • Use world-class developer tool chains for build, security, and stability.

The existing Omaha/Keystone design, implementation, and production issues apply to this project as well.