tree: 958c87e2c3568d484f47cbebe2a56b5dcc609dab [path history] [tgz]
  1. app/
  2. mac/
  3. server/
  4. test/
  5. tools/
  6. win/
  7. BUILD.gn
  8. DEPS
  9. OWNERS
  10. README.md
  11. action_handler.h
  12. branding.gni
  13. configurator.cc
  14. configurator.h
  15. constants.cc
  16. constants.h
  17. crash_client.cc
  18. crash_client.h
  19. crash_reporter.cc
  20. crash_reporter.h
  21. installer.cc
  22. installer.h
  23. installer_mac.cc
  24. installer_win.cc
  25. patcher.cc
  26. patcher.h
  27. persisted_data.cc
  28. persisted_data.h
  29. persisted_data_unittest.cc
  30. prefs.cc
  31. prefs.h
  32. prefs_unittest.cc
  33. registration_data.cc
  34. registration_data.h
  35. run_all_unittests.cc
  36. unzipper.cc
  37. unzipper.h
  38. update_apps.h
  39. update_apps_mac.mm
  40. update_apps_win.cc
  41. update_service.h
  42. update_service_in_process.cc
  43. update_service_in_process.h
  44. updater.cc
  45. updater.h
  46. updater_unittest.cc
  47. updater_version.h.in
  48. util.cc
  49. 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.