-
Notifications
You must be signed in to change notification settings - Fork 884
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
Allow installing rustup without a toolchain (or allow specifying one) #559
Comments
My current workaround is to:
Which uses twice the disk space due to #555. |
I have the same use case for Ruma's development environment. Not being able to pin a specific version of nightly Rust via rustup-init is causing us pain. |
Would allowing a specific toolchain be as simple as removing this line, or is there something else in the code that forces rustup-init to limit the initial toolchain to a channel name? |
@jimmycuadra Yes, removing that line will allow arbitrary toolchains at install. If we do that though it will make it much easier to generate an error during install by selecting a bogus toolchain so the error handling will have to be considered. I'd be happy to take a patch that just removes that line for now. The error handling when the default toolchain fails to install needs revisiting in general. |
You can with following command.
|
I'm building some Docker containers and throwing Rust in there:
This will download and install stable Rust, but I need more control over which version gets installed. Specifically, I'd like to just install rustup, and then install a specific
{stable,beta,nightly}-$DATE
:I'd also be happy if I could pick a specific version straight-off:
I'd be happy to contribute if you have a preferred solution and can give some general pointers as to where to look.
The text was updated successfully, but these errors were encountered: