{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreibuws7wd5vearjbnjsz5w44k6tergywluy32j545udrv6pkq7r4yq",
    "uri": "at://did:plc:ivbknywyskln22er3nkssdhl/app.bsky.feed.post/3mkpr6mv34gb2"
  },
  "path": "/t/pre-rfc-proposal-bound-cargos-implicit-upward-discovery-for-config-toml-files/24210#post_6",
  "publishedAt": "2026-04-30T12:49:01.000Z",
  "site": "https://internals.rust-lang.org",
  "textContent": "Partial workaround: If you can have a directory path that is clean from unwanted configs, you can `cd` to it and use `--manifest-path=/elsewhere/Cargo.toml` to separate Cargo's config search (relative to cwd) from the location of the crate being built.\n\nCrates invoking `cargo` from `build.rs` will unfortunately revert to their own crate's cwd.",
  "title": "[Pre-RFC] Proposal: bound Cargo's implicit upward discovery for config.toml files"
}