blink_rename_merge_helper: Implement run.py loader stub

tools/blink_rename_merge_helper/README.md

Index: tools/blink_rename_merge_helper/README.md
diff --git a/tools/blink_rename_merge_helper/README.md b/tools/blink_rename_merge_helper/README.md
new file mode 100644
index 0000000000000000000000000000000000000000..f33406cdc4e792486d312cc4921d7bf63d241c05
--- /dev/null
+++ b/tools/blink_rename_merge_helper/README.md
@@ -0,0 +1,14 @@
+Tool to help manage merge conflicts from the Blink rename. The tool is committed
+into the Chromium repository. However, with the exception of the `run.py` loader
+stub, everything else is fetched from the chromium-blink-rename Google Storage
+bucket at runtime.
+
+COMPONENTS is a list of component names and hashes; the checked-in copy only
+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 like:
- being able to review the diffs
- being able to go back to a known good version if something breaks
- etc

basically all the good things source control gives us. Not sure how to word this
sentence tbh

[danakj, 2017/04/05 21:55:08]

As a mirror to what is in gs so that we can see and review what is there more
easily. Any changes to the gs should be checked in to that file also?

[dcheng, 2017/04/05 22:21:34]

Done.

+from Google Storage and uses that. In addition, if the component name is of the
+form `name-platform`, `name` is used as the actual component name, while
+`platform` is passed to `download_from_google_storage.py` as the platform
+argument. This is used to version per-platform binaries.
+
+Use `upload_to_google_storage.py -b chromium-blink-rename -a pylib` to upload
+new versions of the pylib.