Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 Tool to help manage merge conflicts from the Blink rename. The tool is committed | |
| 2 into the Chromium repository. However, with the exception of the `run.py` loader | |
| 3 stub, everything else is fetched from the chromium-blink-rename Google Storage | |
| 4 bucket at runtime. | |
| 5 | |
| 6 COMPONENTS is a list of component names and hashes; the checked-in copy only | |
| 7 exists for tracking purposes, as the tool always fetches the latest COMPONENTS | |
|
danakj
2017/04/05 21:38:51
what do u mean by tracking?
dcheng
2017/04/05 21:44:39
Hmm... I'm trying to say that it's used for things
danakj
2017/04/05 21:55:08
As a mirror to what is in gs so that we can see an
dcheng
2017/04/05 22:21:34
Done.
| |
| 8 from Google Storage and uses that. In addition, if the component name is of the | |
| 9 form `name-platform`, `name` is used as the actual component name, while | |
| 10 `platform` is passed to `download_from_google_storage.py` as the platform | |
| 11 argument. This is used to version per-platform binaries. | |
| 12 | |
| 13 Use `upload_to_google_storage.py -b chromium-blink-rename -a pylib` to upload | |
| 14 new versions of the pylib. | |
| OLD | NEW |