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