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?

  • @LorgresOP
    2•8 months ago

    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?

    • 4wd
      1•8 months ago

      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:

      1. Title
      • Brief description of the project
      • Features
      1. Build
      • List of supported OS
      • List of dependencies (what packages do I need to build your application)
      • Commands to build the application (what do I need to do to build your application)
      • Binary Locations (where can I find the built binary)
      1. Usage
      • Program arguments (what do I need to provide to use your CLI application)

      You can find an example here. I’m not saying this is the best README, but I think it’s simple and informative.