tree: 4be6468d5595300836289158365b63ec1bffbe87 [path history] [tgz]
  1. app/
  2. device_management/
  3. mac/
  4. protos/
  5. test/
  6. tools/
  7. win/
  8. BUILD.gn
  9. DEPS
  10. OWNERS
  11. README.md
  12. action_handler.h
  13. branding.gni
  14. configurator.cc
  15. configurator.h
  16. constants.cc
  17. constants.h
  18. control_service.h
  19. control_service_in_process.cc
  20. control_service_in_process.h
  21. crash_client.cc
  22. crash_client.h
  23. crash_reporter.cc
  24. crash_reporter.h
  25. crx_downloader_factory.h
  26. external_constants.cc
  27. external_constants.h
  28. external_constants_impl.h
  29. external_constants_mac.mm
  30. external_constants_mac_unittest.mm
  31. external_constants_unittest.cc
  32. external_constants_unittest.h
  33. external_constants_win.cc
  34. external_constants_win_unittest.cc
  35. installer.cc
  36. installer.h
  37. installer_mac.cc
  38. installer_win.cc
  39. lib_util.h
  40. lib_util_mac.mm
  41. lib_util_unittest.cc
  42. lib_util_win.cc
  43. patcher.cc
  44. patcher.h
  45. persisted_data.cc
  46. persisted_data.h
  47. persisted_data_unittest.cc
  48. policy_manager.cc
  49. policy_manager.h
  50. policy_manager_unittest.cc
  51. prefs.cc
  52. prefs.h
  53. prefs_impl.h
  54. prefs_mac.mm
  55. prefs_unittest.cc
  56. prefs_win.cc
  57. registration_data.cc
  58. registration_data.h
  59. run_all_unittests.cc
  60. service_factory_win.cc
  61. service_scope.h
  62. tag.cc
  63. tag.h
  64. tag_unittest.cc
  65. unittest_util.cc
  66. unittest_util.h
  67. unittest_util_unittest.cc
  68. unzipper.cc
  69. unzipper.h
  70. update_apps_mac.mm
  71. update_service.cc
  72. update_service.h
  73. update_service_in_process.cc
  74. update_service_in_process.h
  75. updater.cc
  76. updater.h
  77. updater_unittest.cc
  78. updater_version.h.in
  79. util.cc
  80. util.h
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.