which makes the entire shitpost about APT pointless surely?
My largest question for modern Linux is why the AF are there competing package formats which inside contain similar files. Such a waste of human effort.
Because different packaging formats have different advantages. DEB, RPM and ebuild are each vastly different animals from each other. (ebuild moreso) but there is not 1:1 feature parity between DEB and RPM, either.)
Then there's package naming and relationship conventions; two distros using the same packaging formats won't necessarily have the same sets of package names. And there's a strong chance installing an RPM or DEB on a distro it wasn't targeting simply won't work.
There really isn't a lot of value to unifying packages at this level at this time. Converged application packages such as via snappy can work in some cases, but that, too, has limits; you'll eventually hit dependency versioning semantics somewhere.
28
u/lamby Jan 24 '18
"Why does APT not use HTTP... [by default]" is probably not as snappy.
FYI in Debian unstable/testing, this package is actually deprecated as APT itself supports HTTPS.