Right now my 'connchk' project is really only available if you're a #Rust user who can `cargo install connchk`.
This weekend I think I'll add some automation to at least provide binaries for x86_64-unknown-linux-gnu, armv7-unknown-linux-gnueabihf, and x86_64-pc-windows-gnu targets. Maybe later I'll package .rpm and .deb versions too.
@ajmartinez Yeah I have the same problem with `hal`, a #Bitcoin CLI tool I made. I should spend some time learning how to package stuff 😅 Ah I think I have an rpm because I used cargo-rpm, but it's apparently not 100% following rpm standards. Would like to get it in #Arch's AUR though. Keep us posted if you make packaging progress!
@stevenroose check out fpm for making packages. Pretty easy to use.
@ajmartinez Hmm, it doesn't have any #Rust-specific docs, so I suppose for binaries created with Rust we can just package the binary and not care about the runtime dependencies (as cargo minimizes those to ones that really every system has)?
@stevenroose and yes for the fpm case I’d use it with the same form as done in the docs here: https://fpm.readthedocs.io/en/latest/source/dir.html
Just ship your binary, any applicable config defaults, docs, and your license. You can declare system dependencies as well, and should if they exist. Help options on fpm are a little better than the docs these days to be honest.
