Hi, I’m looking to open-source a small CLI application I wrote and I’m struggling with how to provide the built app since just providing the binary will not work. I had a friend test it and he had to compile from source due to glibc version differences.
My first thought was providing it as a flatpak but that isn’t really suitable for CLI software.
I’ve googled around a bit and most guides I find just mention packaging separately for multiple package managers/formats (rpm, apt etc.). This seems really inefficient/hard to maintain. What is the industry standard for packaging a Linux software for multi-distro use?
Just build the app on very old distros like Ubuntu 16.04 if possible. But in general, packaging should be handled by the maintainer. If you want to be both a developer and maintainer, packaging problems will take up 75% of your time.
It’s not really hard for us users to follow your README and just copy the built binary to
~/.local/bin.Hi thanks for the reply. Could you elaborate on why building for an old distro may be benefitial/a good solution? Thanks for mentioning this developer/maintainer dynamic. It’s not a concept I was aware of.
Do you have any projects with good READMEs you could point me to, so I can get an idea of what’s important to address?
If you build your app with glibc 2.32 and then run it with glibc 2.39, it will run fine. But it won’t work the other way around.
There is no best README template, but for my personal projects I use this:
You can find an example here. I’m not saying this is the best README, but I think it’s simple and informative.