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