OLD | NEW |
1 # Windows binary tool bootstrap | 1 # Windows binary tool bootstrap |
2 | 2 |
3 This directory has the 'magic' for the `depot_tools` windows binary update | 3 This directory has the 'magic' for the `depot_tools` windows binary update |
4 mechanisms. | 4 mechanisms. |
5 | 5 |
6 ## Software bootstrapped | 6 ## Software bootstrapped |
7 * Python (https://www.python.org/) | 7 * Python (https://www.python.org/) |
8 * Git for Windows (https://git-for-windows.github.io/) | 8 * Git for Windows (https://git-for-windows.github.io/) |
9 * Subversion (https://subversion.apache.org/) | 9 * Subversion (https://subversion.apache.org/) |
10 | 10 |
(...skipping 20 matching lines...) Expand all Loading... |
31 * Original: `https://github.com/git-for-windows/git/releases` | 31 * Original: `https://github.com/git-for-windows/git/releases` |
32 * Mirror: `gs://chrome-infra/PortableGit*.7z.exe` | 32 * Mirror: `gs://chrome-infra/PortableGit*.7z.exe` |
33 | 33 |
34 #### Updating git version | 34 #### Updating git version |
35 1. Download the new `PortableGit-X.Y.Z-{32,64}.7z.exe` from the | 35 1. Download the new `PortableGit-X.Y.Z-{32,64}.7z.exe` from the |
36 git-for-windows release page. | 36 git-for-windows release page. |
37 1. From either console.developers.google.com or the CLI, do: | 37 1. From either console.developers.google.com or the CLI, do: |
38 1. Upload those to the gs://chrome-infra Google Storage bucket. | 38 1. Upload those to the gs://chrome-infra Google Storage bucket. |
39 1. Set the `allUsers Reader` permission (click the "Public link" checkbox | 39 1. Set the `allUsers Reader` permission (click the "Public link" checkbox |
40 next to the binaries). | 40 next to the binaries). |
41 1. Edit the `set GIT_VERSION=X.Y.Z` line in `win_tools.bat` to be the new | 41 1. Edit the `git_version.txt` or `git_version_bleeding_edge.txt` file to |
42 version. | 42 be the new version. |
43 1. At the time of writing, the first version is the default version, and | 43 1. You can use the bleeding edge version to get early feedback/stage a |
44 the second is the 'bleeding edge' version. You can use the bleeding edge | 44 rollout/etc. Users can select this version by 'touch'ing the |
45 version to get early feedback/stage a rollout/etc. | 45 `.git_bleeding_edge` file in the root depot_tools directory. |
46 1. Commit the CL. | 46 1. Commit the CL. |
47 | 47 |
48 Note that in order for the update to take effect, `gclient` currently needs to | 48 Note that in order for the update to take effect, `gclient` currently needs to |
49 run twice. The first time it will update the `depot_tools` repo, and the second | 49 run twice. The first time it will update the `depot_tools` repo, and the second |
50 time it will see the new git version and update to it. This is a bug that should | 50 time it will see the new git version and update to it. This is a bug that should |
51 be fixed, in case you're reading this and this paragraph infuriates you more | 51 be fixed, in case you're reading this and this paragraph infuriates you more |
52 than the rest of this README. | 52 than the rest of this README. |
53 | 53 |
54 ### Python | 54 ### Python |
55 | 55 |
56 Python installs are sourced from gs://chrome-infra/python276_bin.zip . | 56 Python installs are sourced from gs://chrome-infra/python276_bin.zip . |
57 | 57 |
58 The process to create them is sort-of-documented in the README of the python | 58 The process to create them is sort-of-documented in the README of the python |
59 zip file. | 59 zip file. |
60 | 60 |
61 ### Subversion | 61 ### Subversion |
62 | 62 |
63 Subversion installs are sourced from gs://chrome-infra/svn_bin.zip . | 63 Subversion installs are sourced from gs://chrome-infra/svn_bin.zip . |
64 | 64 |
65 There will likely never be an update to SVN in `depot_tools` from the current | 65 There will likely never be an update to SVN in `depot_tools` from the current |
66 version. | 66 version. |
OLD | NEW |