fix!(config): re-enable active toolchain installation in Cfg::find_active_toolchain()
with optional opt-out
#4214
+124
−74
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Following @djc's previous statement at #4211 (comment), I sincerely apologize for all the previous issues related to the abrupt breaking change without enough clarity and transparency, and, if a well-organized public discussion allows this change to happen, a potential experimental stage with a properly-extended migration period.
This PR tries to mitigate #4211 by introducing a new environment variable
RUSTUP_AUTO_INSTALL
that defaults to1
and is subsumed under. This environment variable, when evaluated toCI
true
, will try to install the active toolchain inCfg::find_active_toolchain()
.@rust-lang/rustup please feel free to change this PR as you see fit so that we can land the fix as promptly as possible.
Concerns
Remaining work around this PR might include: