Linux Packaging Debate

Comments debate whether developers should provide distro-specific packages like RPMs or DEBs, or rely on distribution maintainers for open source software, highlighting packaging complexities and alternatives like Flatpak or shell scripts.

📉 Falling 0.5x DevOps & Infrastructure
4,662
Comments
20
Years Active
5
Top Authors
#1384
Topic ID

Activity Over Time

2007
2
2008
21
2009
44
2010
80
2011
73
2012
177
2013
166
2014
243
2015
322
2016
400
2017
285
2018
253
2019
243
2020
392
2021
441
2022
313
2023
469
2024
385
2025
333
2026
20

Keywords

e.g guixsd.org AUR APKBUILD job.html goktug.deb DebConf APKBUILDS GCC GNU packages package distro distros debian linux arch packaging source arch linux

Sample Comments

man8alexd Oct 14, 2025 View on HN

Have you tried building rpm/deb packages?

fsmv Apr 29, 2024 View on HN

Normally it's not your job to package it yourself the distro maintainers do that

andrewshadura Jul 8, 2020 View on HN

Why would anyone use this instead of distro packages?

weirdtunguska Nov 6, 2015 View on HN

Why can't this be done using standard ways, like deb packages?

chlorion Mar 3, 2022 View on HN

Creating packages for various distros is not your job as a software developer, and it never was intended to be your job in the first place. At least part of this stance is based on a misunderstanding of how Linux package manager style software distribution works.You most likely don't have experience creating and maintaining packages for every distro that exists, expecting you to be able to do this would be silly. Typically the users or developers of the countless different distros will b

sreevisakh Aug 18, 2022 View on HN

Can you elaborate a bit on what you mean? It's a bit difficult to install build artifacts directly into the system. There are problems like tracking version compatibility, installing resource files and tracking artifacts for removal etc. This is what packages and package managers do. If you wish to take that route, then Arch PKGBUILDs and Gentoo Ebuilds are reasonably easy. Ebuilds have a lot of similarity with ports. Debian's checkinstall is also somewhat successful in it. Nix and Gui

mercurial May 15, 2013 View on HN

Github is not a substitute for a packaging system.

IceWreck Oct 15, 2021 View on HN

If its open source then packagers will do the job for me

bravetraveler Dec 27, 2022 View on HN

I'm with you! If you're serious about your software (read: you want users)... either make a Flatpak manifest, package spec, or something equivalent.Point is, somebody made something better than this little install shell script. I'll accept pip, I'm not picky.There is almost surely no reason for $thing to be writing to my system directories. Nobody should be coaching this, it can go wrong in every way.Binaries and libraries can come from my home d

rjeli Jul 13, 2020 View on HN

As a big debian fan who runs it on everything... apt works great, yeah, but packaging itself is a nightmare. Try to source patch one of your packages and rebuild it, and maybe distribute it internally. It’s a mess. Haven’t used Arch but e.g. APKBUILDS are heaven in comparison.