Old toolchains kept around, not updated
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
I have a browser bookmark to a local copy of Rust Nightly’s docs, kept up to date by rustup. Lately I had noticed discrepancies between that and doc.rust-lang.org, and assumed that Nightly was slightly late compared to master.
It turns out that, at some point, rustup started including the host(?) triple in the toolchain’s directory name, e.g. $RUSTUP_HOME/toolchains/nightly-x86_64-unknown-linux-gnu. But a $RUSTUP_HOME/toolchains/nightly directory (and beta and stable) was still there, with some never-updated older version, and that’s what I was looking at.
Should rustup.rs remove these old toolchains automatically?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are named. Start with rustup's handling of $RUSTUP_HOME/toolchains, comparing host-triple directories with legacy nightly, beta, and stable directories; completion would require an agreed behavior for automatically handling old toolchains without affecting current ones.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100