3 ms·
Deb/apt might have been nicer to use, but as a packager I found the packaging format extremely horrible to work with. There's a very complex interaction betwee
by xioxox 8y ago
Deb/apt might have been nicer to use, but as a packager I found the packaging format extremely horrible to work with.
There's a very complex interaction between the various files which define a package. It's extremely hard to find out what debhelper and its associated commands are actually doing and to debug them, particularly if you're trying to split a package into multiple parts. I gave up several times trying to make my package before finally succeeding with a simplified version. I'm not sure I will understand how it works when I go back to it.
On top of that the sheer volume of rules and regulations, different packaging helpers and out of date suggestions just added to the problem.
Deb has far too much magic. Rpm is much clearer. I can define a simple configuration file which takes the source, patches it, builds it, and describes the packaged files. I've never had a problem understanding an rpm source package.
- dredmorbius 8y agoThat's because APT serves the user rather than the developed. As a sysadmin, of one box or 100k boxen, I'd have a hell of a lot less apprehension about installing a DEB than an RPM. Thanks largely to Debian Policy, which governs how packaages will behave. The fact that Debian has an order of magnitude more in-repo, in-distro packages also counts for something. As well as the fact that I can start with a minimal installation and add to it only what the box actually needs, a process Red Hat and RPM have never adequately supported. Source: Have run both, personally and professionally, for nearing a quarter century.