-
Notifications
You must be signed in to change notification settings - Fork 893
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
self update after updating a specific toolchain #1605
Conversation
r=me with green CI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty OK with this in general, though the amount of tests needing --no-self-update
I wonder if it might be better to also have a RUSTUP_SUPPRESS_SELF_UPDATE
type environment variable which we could set by default in most of the expect_ok()
calls.
Nothing blocking a merge IMO though.
) | ||
.arg( | ||
Arg::with_name("no-self-update") | ||
.help("Don't perform self update when running the `rustup` command") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be:
.help("Don't perform self update when running the `rustup install` command")
perhaps?
) | ||
.arg( | ||
Arg::with_name("no-self-update") | ||
.help("Don't perform self update when running the `rustup` command") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ditto here but with
.help("Don't perform self update when running the `rustup toolchain install` command")
perhaps?
r? @alexcrichton
This will make sure people who do
rustup update stable
still get a new rustup