Decide what it means to specify a profile for an already installed toolchain
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 22h 40m
- Merged PRs (30d)
- 46
Description
There are a number of circumstances in which rustup might be caused to update an already installed toolchain. In some of those circumstances, the user may be able to specify a profile on the CLI.
Currently we always ignore any profile specified if the toolchain is already installed. This means that if the user specifies default but the installed toolchain has only minimal components, then we will not go ahead and add the extra components. Ditto if the toolchain installed has extra components, we will not remove them.
There may be merit in constraining the component selection to meet the profile specified in certain circumstances. To that end, this issue is here to attempt to encourage discussion on:
- what the situations are now where profile specification is ignored
- which, if any, of those should have some effect
- what that effect ought to be.
/cc @lzutao @rbtcollins
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
The issue names no files, tests, or entry points. Begin by documenting the current situations where rustup ignores a profile for an installed toolchain, then resolve which situations should honor it and what component-selection behavior should result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100