Who is .cargo/config.toml meant for? #14565
Labels
A-configuration
Area: cargo config files and env vars
S-needs-info
Status: Needs more info, such as a reproduction or more background for a feature request.
https://doc.rust-lang.org/cargo/reference/overriding-dependencies.html#paths-overrides suggests that
cargo/config.toml
isn't expected to be included in version control (I mean, why would editing one verion-controlled file be better than editing another?), but I don't see anything like that actually specified on https://doc.rust-lang.org/cargo/reference/config.html.It was hoping to see something along the lines of "
.cargo/config.toml
is intended for local configuration and it's best if you can avoid adding one to version control" , or perhaps an additonal file for user-specific config, in the style of https://learn.microsoft.com/en-us/visualstudio/msbuild/customize-your-local-build?view=vs-2022#user-file, to use for settings that are specific to the user, their machine, or what they are tinkering with at the moment.If
.cargo/config.toml
is actually meant to be shared in version control, then I suppose this is a feature request to add a.cargo/config.local.toml
or.cargo/config.user.toml
to the hierarchy before each.cargo/config.toml
(except$CARGO_HOME/config.toml
, which is clearly supposed to be user-specific already).Otherwise, this is a docs bug.
The text was updated successfully, but these errors were encountered: