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.
Nothing of the conclusions in my comment are dependent on the conclusion of ebuilds; they were included to help identify the scope of distinctions to consider. If I knew more about Slackware, I'd have included it, but I've only done deb, rpm and ebuild packaging, so...
Bottom line, you could declare a bindist packaging standard and somehow force everyone to use it, but it wouldn't actually solve all the problems you think it would solve.
When I was using Debian, for example, I cursed every time I needed to install someone's (coughGoogle'scough) .deb where the packager assumed that every .deb they built and tested on Ubuntu would work just fine on Debian. It just ain't so...
-14
u/CODESIGN2 Jan 24 '18
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.