Is this the right way to build a Debian package for Rust library recently? Should I switch to cargo-deb?

Note: I didn't fill all metadata yet.

https://codeberg.org/mekong-lang/wordcut-engine/src/branch/debian/debian

#Debian #Rust

@veer66 Depends on the use case. Do you want to get the package into Debian proper? Then the most streamlined way is to publish the crate(s) to crates.io and use the https://salsa.debian.org/rust-team/debcargo-conf/ way of creating packages. As long as your package meets the policy requirements, your method would work for that as well, but is a liitle more off the primary route. If you just want to provide a package for users in an extra repo maintained by yourself, either way would work, including cargo-deb.

@veer66 Because you're hosting the code on codeberg.org, definitely look into their repository hosting functionality. I use that in combination with cargo-deb for a small cli utility named `pibtool`, and it works quite well for that usecase (although I had to package `cargo-deb` by myself for that as well to be available).

https://codeberg.org/pib/-/packages
https://codeberg.org/pib/pibtool
https://forgejo.org/docs/latest/user/packages/debian/

@silwol Thank you. With this approach, I have hope that I can finish this in my lifetime.

@werdahias Thank you. My goal is to publish a package similar to librsvg-dev, which the wiki must be helpful.

https://codeberg.org/mekong-lang/wordcutw