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?

  • ⸻ Ban DHMO 🇦🇺 ⸻@aussie.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    9 months ago

    Just make sure you have good build instructions and maybe an install target to put it in /usr/local/bin

    If you’re using C/C++ with Meson it will handle this for you, so long as your targets have install: true set. As other users have said it may get picked up eventually by a distro.

    If you want to create packages there is this tool which is used by LACT (AMD GPU overclocking tool) to generate rpms and debs from a single manifest: https://github.com/vv9k/pkger/