cargo package --list issue with relative path

[messense]

While investigating conda-forge/ruff-feedstock#84 (comment), I found that cargo package --list behaves weird when relative path is used in metadata, for example ruff_cli specifies readme = "../README.md", but cargo package --list outputs

$ cargo package --list --manifest-path ruff_cli/Cargo.toml 2>/dev/null
.cargo_vcs_info.json
Cargo.lock
Cargo.toml
Cargo.toml.orig
README.md
src/args.rs
src/cache.rs
src/commands.rs
src/diagnostics.rs
src/iterators.rs
src/lib.rs
src/main.rs
src/printer.rs
src/resolve.rs
src/updates.rs
tests/black_compatibility_test.rs
tests/integration_test.rs

The result is that the README.md is missing from top level directory in sdist.

[konstin]

this seems partially by design (rust-lang/cargo#7938 (comment)). i think we should ask the cargo developers for an option specifically for tool such as maturin that prints all paths that cargo would include (and in the meantime use custom workarounds)

[messense]

Right, cargo package without --list isn't a viable option for us since there might be non-crates.io path dependencies without version.

https://doc.rust-lang.org/cargo/commands/cargo-package.html#description

[messense]

Relative readme field is no longer an issue after #1741.

We're effectively using cargo metadata | jq '.packages[] | select(.name == "<package-name>") | .readme' to get the path. See also rust-lang/cargo#11666 (comment)