-
Notifications
You must be signed in to change notification settings - Fork 952
Add a component "analysis" #935
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
Comments
If I'm reading this correctly, rustup can install anything that's listed in the channel manifest without needing any change. But the channel manifests currently don't list the analysis files. |
@Arnavion, Could you write what steps I should do to make rustup install analysis files please? |
I'm saying you can't do anything in rustup to fix it. The list of components rustup can install comes from Edit: Here, I think. Edit 2: This commit seems to have added support for it. Not sure why latest nightly's manifest doesn't have it still. Maybe next one will have it. |
@nrc, |
2017-02-03's nightly's manifest contains |
@Arnavion, |
@KalitaAlexey For now, you can do this:
We'll also need to update RLS to use this path instead of its custom one. |
This is work in progress, but I don't think there is anything left to do on the Rustup side (just RLS stuff to address). |
Hello @nrc, |
@KalitaAlexey this should be fixed now, I think there was a PR a while ago which addressed it. |
@nrc, |
I'm not entirely sure, I wouldn't think you need to reinstall Rustup, but perhaps? |
It was fixed for some time after my PR, but newer nightlies' manifests don't have the extension at all. Edit: I assume this is because of the new release infra that doesn't use buildbot. |
So @nrc's change needs to be ported to x.py |
Hi.
Currently RLS is under development.
It uses analysis from https://static.rust-lang.org/dist/index.html
It would be cool if I could execute
rustup component add analysis
and each time I do
rustup update
it would update analysis's files.How hard is it to implement?
Thanks
The text was updated successfully, but these errors were encountered: