3 ms·

I'm not qualified to comment on the larger Debian ecosystem, but having been forced (due to work) to create some Debian packages... the tooling is awful. Packag

I'm not qualified to comment on the larger Debian ecosystem, but having been forced (due to work) to create some Debian packages... the tooling is awful. Packages are two(?) layers of tarballs, there's the option of free-form shell scripts in there to do whatever as a pre/post-install step, etc. etc. There's even several ways to try to hide some of that awfulness under the carpet, and yet it's still there. If they want to attract people who care in the least about developer experience they'll need to consolidate and fix their package system and tooling.

homebrewer 2y ago
Search HN for "Debian packaging", it's a very old issue that's been discussed at length. Apparently the solution is to write yet another automation utility: https://people.debian.org/~nthykier/blog/2023/a-new-debian-package-helper-debputy.html https://people.debian.org/~nthykier/blog/2023/a-new-debian-p... Personally I have given up on Debian packaging. Work applications get shoved into /opt and configured via Ansible, and desktop systems run other distributions with simpler packaging formats (with internal or home stuff wrapped into proper packages). I've thought about alternatives for the servers, but Alpine et al have their own issues. Nothing has been decided yet.