Skip to content
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

Support rustup-init --default-toolchain none #1257

Merged
merged 1 commit into from
Oct 6, 2017

Conversation

petrochenkov
Copy link
Contributor

@petrochenkov petrochenkov commented Sep 22, 2017

To address this use case #309 (comment).

This is especially useful when user directories have quotas into which large components (e.g. docs) do not fit.

@petrochenkov
Copy link
Contributor Author

ping @Diggsey @alexcrichton

@alexcrichton
Copy link
Member

@petrochenkov oh oops sorry, thanks for the ping!

Just to clarify, what's the behavior of the rustc/cargo/etc shims in this scenario? If you avoid installing a toolchain, what does cargo --version do, for example?

@petrochenkov
Copy link
Contributor Author

@alexcrichton

$ cargo --version
error: no default toolchain configured

$ rustc --version
error: no default toolchain configured

@alexcrichton
Copy link
Member

Ok sounds great!

@bors: r+

@bors
Copy link
Contributor

bors commented Oct 6, 2017

📌 Commit d93c1c8 has been approved by alexcrichton

@bors
Copy link
Contributor

bors commented Oct 6, 2017

⌛ Testing commit d93c1c8 with merge c0ee150...

bors added a commit that referenced this pull request Oct 6, 2017
Support `rustup-init --default-toolchain none`

To address this use case #309 (comment).

This is especially useful when user directories have quotas into which large components (e.g. docs) do not fit.
@bors
Copy link
Contributor

bors commented Oct 6, 2017

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing c0ee150 to master...

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

Successfully merging this pull request may close these issues.

3 participants