In https://github.com/rust-secure-code/cargo-auditable I have started out tagging the versions of cargo auditable itself, but the project has since grown and gained several more binaries. So I have versions like v0.5.0 referring to cargo auditable, and everything else is prefixed, e.g. rust-audit-info/v0.5.4.
This naming scheme causes cargo dist to fail, necessitating workarounds. It detects several packages matching the version from a given tag (even only one package with 0.1.0 version exists on the commit with the 0.1.0 tag).
I cannot change the tagging format because several Linux distributions now rely on monitoring these tags to be informed about new releases. So I would like to configure cargo dist to treat versions such as v0.5.0 as always referring to the package I specify, namely "cargo-auditable".
This would unlock publishing the auxiliary tools such as rust-audit-info and auditable2cdx through cargo dist.
In https://github.com/rust-secure-code/cargo-auditable I have started out tagging the versions of
cargo auditableitself, but the project has since grown and gained several more binaries. So I have versions likev0.5.0referring tocargo auditable, and everything else is prefixed, e.g.rust-audit-info/v0.5.4.This naming scheme causes
cargo distto fail, necessitating workarounds. It detects several packages matching the version from a given tag (even only one package with 0.1.0 version exists on the commit with the 0.1.0 tag).I cannot change the tagging format because several Linux distributions now rely on monitoring these tags to be informed about new releases. So I would like to configure
cargo distto treat versions such asv0.5.0as always referring to the package I specify, namely "cargo-auditable".This would unlock publishing the auxiliary tools such as
rust-audit-infoandauditable2cdxthroughcargo dist.