this post was submitted on 10 Apr 2024
15 points (100.0% liked)

Learn Programming

1625 readers
2 users here now

Posting Etiquette

  1. Ask the main part of your question in the title. This should be concise but informative.

  2. Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.

  3. Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.

  4. Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
15
How to efficiently package CLI application on linux (self.learn_programming)
submitted 7 months ago by Lorgres to c/[email protected]
12 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Lorgres 2 points 7 months ago (1 children)

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?

[โ€“] [email protected] 1 points 7 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.