Kornel

How did this file get there?

Indeed. Hmm, so cargo-deb needs a good way to distinguish between executables and other executable assets put in the target directory. I could limit stripping only to native rust targets....

I haven't got time to implement this. Could you have a look yourself? There's alredy built_binaries() method that should be plugged in.

No change since https://github.com/mmstick/cargo-deb/issues/67#issuecomment-392337187

I think currently if you define deps as `$auto, libssl (=version)` it will end up outputting `libssl` version twice, because it doesn't combine manual and auto deps intelligently. Try it,...

I'm not sure why `--all` is there. It could be just a simplification/workaround for compatibility with workspaces. I'm slightly worried that there may be crates that have `assets` table in...

> In the case of cargo-deb, the --all option only makes sense if you want to package all the binary crates in the workspace in a single command. I suspect...

This project can't be used to make a package for the official Debian/Ubuntu distribution, because it doesn't follow Debian's requirements to produce source packages first. As for a simple guide...

Placement of generated files is an unsolved problem for Cargo: https://github.com/rust-lang/cargo/issues/5457 I don't want to invent a method for finding these files without coordination with the rest of the ecosystem,...

From the user forum discussion this approach seems most promising: https://matklad.github.io/2018/01/03/make-your-own-make.html given that it can be made to work with plain Cargo without 3rd party tools. So I think we...