-
Mila Green authored
Since on macOS there is no meta installer, the flow to installing an updater is the following: 1. Chrome (or other app) is drag installed. 2. It tries to register itself with the updater. It does that by running its bundled updater, with the --register --app-id=... --version=... command. This is done over RPC, so if there is an updater on the system, it will get the call. If registration is successful, no other action is needed. 3. If no updater is present, the bundled updater will: 3.1. Install itself 3.2. "wake" itself, so that it is promoted. 3.3. Register itself for updates 3.4. Register the app (Chrome, etc.) for updates. Bug: 1109231 Change-Id: I6e3f31ffbb6eaa6334bd9caa708b3b37f883d674 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2350191 Commit-Queue: Mila Green <milagreen@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Cr-Commit-Position: refs/heads/master@{#802261}
3e3058ab