commit | 12da7ef1316328a201176f7776851849cb12d049 | [log] [tgz] |
---|---|---|
author | James Robinson <jamesr@google.com> | Mon Sep 18 16:54:05 2017 -0700 |
committer | James Robinson <jamesr@google.com> | Mon Sep 18 16:54:05 2017 -0700 |
tree | bad4c999ef912d89925998db81e841b681bd463b | |
parent | 62e40219de48857bcae5ad230b1316503e7fc161 [diff] |
[download] Remove directory we will unzip into, not subdir This changes the download behavior for zips to always nuke the directory the archive will unzip into before unzipping instead of trying to delete a subdirectory of the target file. Since our zip archives are downloaded into distinct subdirs, this ensures the downloaded directory matches the archive contents (only) after an update. This mitigates some issues with the Go build that manipulate the directory in //buildtools after downloading to make sure that the local changes are nuked after updates. Change-Id: I008c18af7013cce095511cbc4a6c889fa9561558
This repository contains the hashes of a number of prebuilt tools that are used to build Fuchsia-related projects. The actual tools themselves are located in Google Storage.
In most cases, the jiri
tool will download the build tools automatically during its update
step. To download the tools manually, run update.sh
.
NOTE: These instructions are for Googlers only.
The tarballs are uploaded with the “gsutil” program. See https://cloud.google.com/storage/docs/gsutil
There's a link there to download and install the Google Cloud SDK: https://cloud.google.com/sdk/docs/
After installing the SDK you need to initialize/authenticate: https://cloud.google.com/storage/docs/gsutil_install#authenticate
One of the steps will ask you for a cloud project. Choose loas-fuchsia-team.
At this point you can use gsutil to upload/download tarballs, view cloud directory contents, and so on.
Tarballs must have the tool name as the top level directory. E.g.,
bash$ tar tvf qemu.tar.bz2 drwxr-xr-x ... qemu/ drwxr-xr-x ... qemu/libexec/ ...
The uploaded file name is the sha1 hash of the tarball. It could also be a sha1 hash of the tarball contents, avoiding unnecessary spurious differences in uploads.
To compute the latter, one can do something like:
bash$ LC_ALL=POSIX cat $(find qemu/ -type f | sort) | shasum -a1
The sha1 hash is checked into the buildtools repo and supports adding new tarballs or rolling back to a previous one. See the *.sha1 files in buildtools/{mac,linux64}.
There are separate directories for mac and linux tarballs. E.g.,
bash$ ./bin/gsutil ls gs://fuchsia-build/fuchsia/qemu/mac gs://fuchsia-build/fuchsia/qemu/mac/ gs://fuchsia-build/fuchsia/qemu/mac/10d77d7df5b39440148ac3aab1a401ff42337a76 ... bash$ ./bin/gsutil ls gs://fuchsia-build/fuchsia/qemu/linux64 gs://fuchsia-build/fuchsia/qemu/linux64/ gs://fuchsia-build/fuchsia/qemu/linux64/10d77d7df5b39440148ac3aab1a401ff42337a76 ...