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