rust-lang / rust-lang/rust-forge

infra/channel-layout: Explain `channel-rust-stable` and `channel-rust-nightly`

Open
#760 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-bug T-infra
Dominant language
Rust
Stars
568
Forks
253
Avg merge
5h 33m
Merged PRs (30d)
12

Description

https://forge.rust-lang.org/infra/channel-layout.html
I can understand what the channel-rust-stable.toml and channel-rust-nightly.toml are, but what are their counterparts without the .toml extension?

https://static.rust-lang.org/dist/channel-rust-stable
https://static.rust-lang.org/dist/channel-rust-nightly

From these links, Mozilla Firefox 115.13.0esr respectively downloads the files channel-rust-stable.gz and channel-rust-nightly.gz, which, however, are not compressed data, but plain text files containing the following (as of today):

channel-rust-stable.gz
rust-1.16.0-aarch64-unknown-linux-gnu.tar.gz
rust-1.16.0-arm-unknown-linux-gnueabihf.tar.gz
rust-1.16.0-arm-unknown-linux-gnueabi.tar.gz
rust-1.16.0-armv7-unknown-linux-gnueabihf.tar.gz
rust-1.16.0-i686-apple-darwin.pkg
rust-1.16.0-i686-apple-darwin.tar.gz
rust-1.16.0-i686-pc-windows-gnu.exe
rust-1.16.0-i686-pc-windows-gnu.msi
rust-1.16.0-i686-pc-windows-gnu.tar.gz
rust-1.16.0-i686-pc-windows-msvc.exe
rust-1.16.0-i686-pc-windows-msvc.msi
rust-1.16.0-i686-pc-windows-msvc.tar.gz
rust-1.16.0-i686-unknown-linux-gnu.tar.gz
rust-1.16.0-mips64el-unknown-linux-gnuabi64.tar.gz
rust-1.16.0-mips64-unknown-linux-gnuabi64.tar.gz
rust-1.16.0-mipsel-unknown-linux-gnu.tar.gz
rust-1.16.0-mips-unknown-linux-gnu.tar.gz
rust-1.16.0-powerpc64le-unknown-linux-gnu.tar.gz
rust-1.16.0-powerpc64-unknown-linux-gnu.tar.gz
rust-1.16.0-powerpc-unknown-linux-gnu.tar.gz
rust-1.16.0-s390x-unknown-linux-gnu.tar.gz
rust-1.16.0-x86_64-apple-darwin.pkg
rust-1.16.0-x86_64-apple-darwin.tar.gz
rust-1.16.0-x86_64-pc-windows-gnu.exe
rust-1.16.0-x86_64-pc-windows-gnu.msi
rust-1.16.0-x86_64-pc-windows-gnu.tar.gz
rust-1.16.0-x86_64-pc-windows-msvc.exe
rust-1.16.0-x86_64-pc-windows-msvc.msi
rust-1.16.0-x86_64-pc-windows-msvc.tar.gz
rust-1.16.0-x86_64-unknown-freebsd.tar.gz
rust-1.16.0-x86_64-unknown-linux-gnu.tar.gz
rust-1.16.0-x86_64-unknown-netbsd.tar.gz
channel-rust-nightly.gz
rust-nightly-aarch64-unknown-linux-gnu.tar.gz
rust-nightly-arm-unknown-linux-gnueabihf.tar.gz
rust-nightly-arm-unknown-linux-gnueabi.tar.gz
rust-nightly-armv7-unknown-linux-gnueabihf.tar.gz
rust-nightly-i686-apple-darwin.pkg
rust-nightly-i686-apple-darwin.tar.gz
rust-nightly-i686-pc-windows-gnu.exe
rust-nightly-i686-pc-windows-gnu.msi
rust-nightly-i686-pc-windows-gnu.tar.gz
rust-nightly-i686-pc-windows-msvc.exe
rust-nightly-i686-pc-windows-msvc.msi
rust-nightly-i686-pc-windows-msvc.tar.gz
rust-nightly-i686-unknown-linux-gnu.tar.gz
rust-nightly-mips64el-unknown-linux-gnuabi64.tar.gz
rust-nightly-mips64-unknown-linux-gnuabi64.tar.gz
rust-nightly-mipsel-unknown-linux-gnu.tar.gz
rust-nightly-mips-unknown-linux-gnu.tar.gz
rust-nightly-powerpc64le-unknown-linux-gnu.tar.gz
rust-nightly-powerpc64-unknown-linux-gnu.tar.gz
rust-nightly-powerpc-unknown-linux-gnu.tar.gz
rust-nightly-s390x-unknown-linux-gnu.tar.gz
rust-nightly-x86_64-apple-darwin.pkg
rust-nightly-x86_64-apple-darwin.tar.gz
rust-nightly-x86_64-pc-windows-gnu.exe
rust-nightly-x86_64-pc-windows-gnu.msi
rust-nightly-x86_64-pc-windows-gnu.tar.gz
rust-nightly-x86_64-pc-windows-msvc.exe
rust-nightly-x86_64-pc-windows-msvc.msi
rust-nightly-x86_64-pc-windows-msvc.tar.gz
rust-nightly-x86_64-unknown-freebsd.tar.gz
rust-nightly-x86_64-unknown-linux-gnu.tar.gz
rust-nightly-x86_64-unknown-netbsd.tar.gz

These links also work and provide what is expected:
https://static.rust-lang.org/dist/channel-rust-stable.sha256
https://static.rust-lang.org/dist/channel-rust-stable.asc
https://static.rust-lang.org/dist/channel-rust-nightly.sha256
https://static.rust-lang.org/dist/channel-rust-nightly.asc

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with infra/channel-layout.html and compare its explanation of the .toml files with the extensionless channel-rust-stable and channel-rust-nightly URLs. Update the page to explain what those plain-text listings represent and how they relate to the .sha256 and .asc files; done means a reader can distinguish each channel artifact.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.