rustup toolchain list should also tell you which toolchains are available. Getting this information correctly will require either indexing it on the backend or having every client index the archives themselves.
Related to https://github.com/rust-lang-nursery/multirust-rs/issues/192
I wish to have something like --json for as many subcommands as possible. It can be any machine-readable formats, not necessarily JSON
Is there a place we can see the available toolchains in the browser right now?
@oconnor663 Not in a user-friendly way, but you can find the toml manifests here: https://static.rust-lang.org/dist/index.html
@Diggsey thanks, that's what I needed.
rustup toolchain list
gives me a list of the installed toolchains, not the available ones.
Yes, please. The only reason I'll ever run rustup toolchain list is because I'm missing one that I expected to have.
This appears to not exist any more (the last Internet Archive snapshot was on 11-11-2018) – is there a replacement?
if you're like me, you probably want rustup target list, because that shows the available target triples, eg x86_64-unknown-linux-musl
Just ran into this while doing my usual google search for a list of toolchains. If you're using fish as your shell, it has dynamic completions for rustup, including a list of targets and toolchains, that are automatically available when performing an operation like rustup toolchain add <TAB>.
For those still looking for a list, after some searching I found this: https://rust-lang.github.io/rustup-components-history/
@jrb467 @packysauce Thank you, good men! And rustup target list does the thing!
The full toolchain channel list would be enormous (since there are lots of nightly toolchains etc). I don't think this kind of feature belongs in rustup. If there's a strong reason to support attempting to enumerate available toolchain channels then please open a fresh issue to discuss it, and we can bring in some of the infra/release team to help us work out what we could do.
Most helpful comment
if you're like me, you probably want
rustup target list, because that shows the available target triples, eg x86_64-unknown-linux-musl