There's no fundamental technical reason Linux couldn't have just 1 extensible package format and 1 extensible package manager. All the reasons for the split are social ("I like A"), political ("we want to be able to control A") or historical ("A came first, we built our house on A, we can't abandon A").
Converting between the differing package formats is actually relatively easy and tools like `alien` exist, that do that.
As I said: social/political/historical reasons bringing us down.
[1] I know about lsb_release, but that's an example of an afterthought, not a part of the initial design.
My point still stands, something like this should have been included from the first releases of Linux distros, 20 years ago. And that was just a random example I came up with after 2 minutes of trying to prove a point. There's many, many more like it.
Also, just for kicks I took at look at the spec and...
1. ANSI_COLOR is funny:
> A suggested presentation color when showing the OS name on the console. This should be specified as string suitable for inclusion in the ESC [ m ANSI/ECMA-48 escape code for setting graphical rendition. This field is optional. Example: "ANSI_COLOR="0;31"" for red, or "ANSI_COLOR="1;34"" for light blue.
2. And some parts are scary:
> parameters may be set using os-release
Oh-oh! Everything is optional! That's really bad for a RFC.
Likewise, different packaging formats exist for different needs. Docker and Ubuntu Snap are for different needs, yet they overlap. Systemd did initially not care about packaging and containers. Yet, there is an overlap, like "How to do logging?". Docker and Systemd both grow and overlap more and more.
We have gratuitous differences which could have been prevented with a better design. See for example even the mess in the rpm world where a SUSE rpm may or may not work on Red Hat.
My hope for systemd is that it unifies the Linux Desktop universe. The Free Desktop movement has stopped doing that.
There is a time for exploding into lots of variants and a time for unifying. Remember the time, when git came up? There was an explosion of DVCSs (Monotone, Darcs, Bazaar, and more). For now, the world has mostly settled on git with Mercurial as a secondary.
I wonder if this proposed system would be as amenable to handling such a wide variety of software (e.g. https://nixos.org/nixpkgs/manual/#chap-language-support ) on such a wide variety of platforms (e.g. https://github.com/NixOS/nixpkgs/tree/master/pkgs/os-specifi... ).
The blog post is dated September 2014. Nix had been around for at least a decade by then (e.g. see https://nixos.org/docs/papers.html ).
Wikipedia says Gobolinux is about the same age as Nix.
This is fundamentally an implementation of Lennart's blog post - http://0pointer.net/blog/revisiting-how-we-put-together-linu.... That article used the words "We want an efficient way that allows vendors to package their software " ... which was followed by a storm of angry systemd-is-the-borg-it-needs-to-die tweets and articles.
Even on HN - the response to this article seems fairly muted... although it is a bigger political issue than even init systems. I wonder what the response would have been to "systemd introduces new portable packaging format"