diff options
| author | Pietro Albini <pietro@pietroalbini.org> | 2020-09-29 15:33:25 +0200 |
|---|---|---|
| committer | Pietro Albini <pietro@pietroalbini.org> | 2020-10-09 15:21:45 +0200 |
| commit | 8d2b15943b0dad58959f5fcac1664bfdd7c201b7 (patch) | |
| tree | 970e1c5df4b8a04140cbc4fd0e4d922e9ddd590c /library/std/src | |
| parent | ccea570488694e502c1a7ca8f3f0866c9b763ce4 (diff) | |
| download | rust-8d2b15943b0dad58959f5fcac1664bfdd7c201b7.tar.gz rust-8d2b15943b0dad58959f5fcac1664bfdd7c201b7.zip | |
bootstrap: always use the Rust version in package names
The format of the tarballs produced by CI is roughly the following:
{component}-{release}-{target}.{ext}
While on the beta and nightly channels `{release}` is just the channel
name, on the stable channel is either the Rust version or the version of
the component we're shipping:
cargo-0.47.0-x86_64-unknown-linux-gnu.tar.xz
clippy-0.0.212-x86_64-unknown-linux-gnu.tar.xz
llvm-tools-1.46.0-x86_64-unknown-linux-gnu.tar.xz
miri-0.1.0-x86_64-unknown-linux-gnu.tar.xz
rls-1.41.0-x86_64-unknown-linux-gnu.tar.xz
rust-1.46.0-x86_64-unknown-linux-gnu.tar.xz
...
This makes it really hard to get the package URL without having access
to the manifest (and there is no manifest on ci-artifacts.rlo), as there
is no consistent version number to use.
This commit addresses the problem by always using the Rust version
number as `{release}` for the stable channel, regardless of the version
number of the component we're shipping. I chose that instead of "stable"
to avoid breaking the URL scheme *that* much.
Rustup should not be affected by this change, as it fetches the URLs
from the manifest. Unfortunately we don't have a way to test other
clients before making a stable release, as this change only affects the
stable channel.
Diffstat (limited to 'library/std/src')
0 files changed, 0 insertions, 0 deletions
