cargo

cargo copied to clipboard

When build fails, print dependency graph path leading to failure

3

### Problem I'm running `cargo build --bin foo` (with cross-compilation, custom compiler, large workspace, feature flags, etc etc). Build fails: ``` ... Compiling openssl-sys v0.9.110 error: failed to run custom...

stepancheg

Allow specifying build dependencies `opt-level` with `[project.dev.build-override.package]`

3

### Problem We have a compiler + VM monorepo with a build step, where we compile a standard library to include into the executable later. The step itself depends on...

mkurnikov

Support inheriting `metadata` from workspace `Cargo.toml`

3

### Problem I tried adding this to my workspace `Cargo.toml` ```toml [workspace.package.metadata.docs.rs] all-features = true targets = ["x86_64-unknown-linux-gnu"] rustdoc-args = ["--generate-link-to-definition"] ``` and inheriting it in a package ```toml [package]...

jhpratt

cargo publish --workspace should fail early if you don't have permission to publish everything

1

### Problem It's possible to have `crates.io` ownership on some -- but not all -- crates in a workspace. In that case, `cargo publish --workspace` might publish a few crates...

jneem

### What it does Users may add the `version` field, thinking its relevant for git/path dependencies when it is instead adding a fallback registry source when published. While we can't...

epage

Option to show semver constraints in `cargo tree`

2

### Problem `cargo tree` currently produces the following output: ``` test1 v0.1.0 (/home/user/test1) |-- clap v4.5.50 | `-- clap_builder v4.5.50 | |-- anstream v0.6.21 `-- toml v0.9.8 |-- anstream v0.6.21...

bhavyakukkar