[Pkg-rust-maintainers] Bug#977491: debcargo: no clear way to indicate that a "feature" is actually a build-dep for a binary crate

Daniel Kahn Gillmor dkg at fifthhorseman.net
Tue Dec 15 16:56:59 GMT 2020

Package: debcargo
Version: 2.4.3-3+b1

I'm looking at the sha1collisiondetection crate.  this crate produces a
library and a binary ("sha1cdsum").

The binary needs to build against the structopt crate, but the library
doesn't need it.

Upstream represents this as the library having a structopt "feature",
which the binary requires.

But debcargo maps this into wanting to produce a "structopt" feature for
the library.  We don't *want* that additional feature package.  Or,
under the new rust packaging regime, we don't want that additional
dependency for the bundled all-Provides librust-*-dev package.

So i'd like for debcargo to have a way to indicate that a particular
feature should be ignored when packaging the library (but not ignored as
a build-depends).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/attachments/20201215/e2b833d3/attachment.sig>

More information about the Pkg-rust-maintainers mailing list