``cargo rpm init`` generates malformed TOML about cargo-rpm HOT 6 CLOSED

Unless I'm missing something this is an annoyance but easily solved, e.g. in my case I modified the following generated Cargo.toml lines and then cargo rpm build worked and the produced RPM file installed cleanly in a CentOS-8 Docker container:

Generated by cargo rpm init

[package.metadata.rpm.targets]
./src/bin/somebinary = { path = "/usr/bin/./src/bin/somebinary" }
./src/bin/someotherbinary = { path = "/usr/bin/./src/bin/someotherbinary" }

Fixed by hand:

[package.metadata.rpm.targets]
somebinary = { path = "/usr/bin/somebinary" }
someotherbinary = { path = "/usr/bin/someotherbinary" }

from cargo-rpm.

Hrmm, I thought we had the case of --bin apps with their main.rs located in src/bin covered (it's one we actually use quite frequently) but after reviewing the apps we package as RPMs I see the ones we deploy are presently all src/main.rs.

So, sorry about that, this is definitely a case we need to support and one which will impact our own apps soon!

from cargo-rpm.

How about this fix ? Will we get this ?

from cargo-rpm.

We'll get it whenever someone has time to contribute it.

from cargo-rpm.

Yeah, this seems like a minor bug in terms of how the paths are computed for the TargetType::MultiBin case

from cargo-rpm.

cargo-rpm is unmaintained: #96

from cargo-rpm.