feat: write (or overwrite) .cargo/config.toml in x.py vendor#1
Merged
Conversation
Initially, this patch was proposed in rust-lang#144124.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Disclaimer
Initially, this patch was proposed in rust-lang#144124.
About
When running the command
x.py vendorthe output contains a part of the output of the cargo vendor command, which tells you what to add to.cargo/config.tomlin order to use the downloaded packages during assembly. This patch adds functionality that allows you to write this information directly to.cargo/config.toml. The only limitation is that if there was already any information in.cargo/config.toml, it will be overwritten.