Closed kpcyrd closed 3 weeks ago
There's also --no-build
option that just picks whatever is already in target/release
.
This will probably conflict with stripping too, so --no-strip
.
Thanks for the hint!
I've checked in regards to --no-strip
and the dependency data is stored in a .dep-v0
section that is left untouched by strip.
Hello!
I'm trying to use cargo-deb and cargo-auditable together, I noticed
cargo deb
has an option to replace thebuild
subcommand with something else so I triedauditable build
but it seems this is taken as an opaque string (actually looking for a/usr/bin/cargo-auditable build
binary).The error looks like this:
I could probably work around this by creating a
cargo-auditable-build
dummy subcommand that callscargo auditable build
for me, passing along all arguments:I think legitimate cargo subcommands are very unlikely to contain spaces, so splitting by space seems fairly safe, but alternatively there could be a
--auditable
flag that internally configures["auditable", "build"]
without changing anything else about existing--cargo-build
behavior.This would allow using
cargo audit bin /usr/bin/...
on files that have been installed with cargo-deb.Thanks!