Philipp Oppermann
Philipp Oppermann
@hardBSDk This PR is still marked as a draft. Is this this ready to be merged? If not, what is missing? Maybe I can help.
@hardBSDk Friendly ping
@jgouly Check out https://internals.rust-lang.org/t/proposal-move-some-cargo-config-settings-to-cargo-toml/13336. The proposal takes a different way than your suggestion, but I think it should help in your use case as well. The good news is that...
#7621 is about ignoring _parent_ config files. This issue is about ignoring all config files (except for the one on the HOME dir). One motivation for this issue is builds...
Maybe I misunderstood #7621 and linked #7620. I thought that it proposed to still apply the config file of the current working dir. So if the project lives at `/a/b/c`,...
Thanks for reopening and sorry for the confusion! > In some tools, I've seen them have an `--isolated` flag that causes it to not implicitly load any config, leaving it...
I think https://github.com/rust-lang/cargo/issues/12738 is also related in a way. Once we can move all project-specific configuration from `.cargo/config` to `Cargo.toml`, there will be less need for such an `--isolated` flag.
That part was motivated by https://github.com/rust-lang/cargo/pull/6026. I thought that settings that are applied even to a `cargo install` are probably not something you want to disable (e.g. network-specific proxy config)....
Unfortunately it is not clear when the `const_mut_refs` feature will be stable, so maybe we need to wait for quite some time. So I would be fine with merging this...
Nice, this looks very promising!