Skip to content

Track missing components #1487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nrc opened this issue Aug 24, 2018 · 4 comments
Closed

Track missing components #1487

nrc opened this issue Aug 24, 2018 · 4 comments

Comments

@nrc
Copy link
Member

nrc commented Aug 24, 2018

So that if a component is missing and the user tries to add it, Rustup can explain. Ideally it could also suggest the last release with the component.

@nrc
Copy link
Member Author

nrc commented Aug 27, 2018

I think this should be fixed by rust-lang/rust#53715

I wish it were easier to test this

@nrc
Copy link
Member Author

nrc commented Aug 27, 2018

it could also suggest the last release with the component

this part is not done, and I'm not sure how to implement it

@sunjay
Copy link
Member

sunjay commented Aug 29, 2018

It would also be really helpful if rustup could ask whether or not you want to continue when upgrading would remove a component you previously had installed. If asking for more input would break stuff, we could also error out when an installation would uninstall a component and have an extra --force flag or something to push the update through anyway.

@kinnison
Copy link
Contributor

I think that current behaviour, especially with profiles and nightly backtracking, solves the intent of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants