{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibz4y2tq6qwgkjxfq6qd7ld2amyrxttf4kwr54fzmfpyidn6kn7qa",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkpxv6mnsvt2"
  },
  "path": "/t/pre-rfc-proposal-bound-cargos-implicit-upward-discovery-for-config-toml-files/24210#post_8",
  "publishedAt": "2026-04-30T14:30:05.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "I actually tried a bit more: `cd /tmp && cargo build --manifest-path=$HOME/some/where/Cargo.toml` works, while `cargo build --manifest-path=\"$HOME/some/where/CArgo.toml\"` fails to build with my broken configuration in `$HOME/.cargo/config.toml`.\n\nSo the work-around you suggested works indeed works for cargo build. Is there a similar work-around for `cargo install`?\n\nI tired to `cargo build` first and then do a `cargo install` as a separate step. Cargo is really thorough: It does not recompile any of the files, but it does notice that the linker has changed and tries to relinking the binary, triggering my broken linker configuration in `$HOME/.cargo/config.toml`.",
  "title": "[Pre-RFC] Proposal: bound Cargo's implicit upward discovery for config.toml files"
}