Just as NixOS, GNU Guix System cannot just run any arbitrary binary built in another GNU/Linux distribution because it does not follow File Hierarchy Standard and so on… But there are workarounds, like patching the binary to change the dynamic loader path.
But one can use Flatpak just fine on GNU Guix System and NixOS.
Appimage requires patching because it is not portable.
As much as an Ubuntu fork that removes that semi-proprietary snap stuff would be in a good position to build a user base quickly, so would now a Debian fork that keeps the on-device code licenses clean.
I didn’t mean running on the top of some distro, but “native” compatibility to existing packaging. Snap/Flatpack/Nix etc. can also more or less run on the top of arbitrary distros, but I think more acceptance can be achieved if the packages are (at least source-level) compatible to something existing and widespread and run as first-class citizens there.
Not saying that Guix isn’t innovative, useful or joyful, though. Just thinking that it might not work as an alternative for Debian in every case.
Will look into PureOS and Trisquel. Are their releases roughly corresponding to some releases of Debian or Ubuntu, respectively (e.g. package-version-wise)?
if the packages are (at least source-level) compatible to something existing and widespread and run as first-class citizens there.
Traditional package managers and formats are so bad… Well Unix, GNU/Linux is a mess.
no current better way around it other than the Nix and Guix way. Flatpak is the 2nd better current model for portability. Today I only package to Nix and Guix; sometimes Flatpak as well.
Guix package manager theorerically can run in any distro so you can use Guix packages in any distro; I run it on NixOS for example. Some distributions have a dedicated package for installing it, or use the official instructions https://guix.gnu.org/en/manual/en/html_node/Binary-Installation.html#Binary-Installation
Just as NixOS, GNU Guix System cannot just run any arbitrary binary built in another GNU/Linux distribution because it does not follow File Hierarchy Standard and so on… But there are workarounds, like patching the binary to change the dynamic loader path.
But one can use Flatpak just fine on GNU Guix System and NixOS.
Appimage requires patching because it is not portable.
There are already PureOS and Trisquel https://www.gnu.org/distros/free-distros.en.html
I suggested GNU Guix System because it is innovative in a very useful and joyful way.
I didn’t mean running on the top of some distro, but “native” compatibility to existing packaging. Snap/Flatpack/Nix etc. can also more or less run on the top of arbitrary distros, but I think more acceptance can be achieved if the packages are (at least source-level) compatible to something existing and widespread and run as first-class citizens there.
Not saying that Guix isn’t innovative, useful or joyful, though. Just thinking that it might not work as an alternative for Debian in every case.
Will look into PureOS and Trisquel. Are their releases roughly corresponding to some releases of Debian or Ubuntu, respectively (e.g. package-version-wise)?
i wrote that 1st paragraph just in case.
2nd paragraph
Traditional package managers and formats are so bad… Well Unix, GNU/Linux is a mess.
no current better way around it other than the Nix and Guix way. Flatpak is the 2nd better current model for portability. Today I only package to Nix and Guix; sometimes Flatpak as well.