Originally posted by starshipeleven
View Post
There are huge advantages if there is one unique package (and package format) to generate an operating runtime package that works on almost all distributions. No need for dozens of spec files, no need for descriptive apt (however they build their stuff). One unique set of permission and permission flags and overall consistency through all the packages. This all set by good rules that every package needs to follow.
The same way when we look in apk files (Android) or their counterparts for Apple. If you look inside their "packages", then you see a unified and unique structure going through all the different software they offer in their repositories (e.g. app store or pay store).
Rather than brewing their own set of "spec" files for building packages, everyone can work on a unified meta-file (or spec file) to build the final runtime.
The thing is - the overall acceptance. For example: It took me quite some time to get along with systemd. But nowadays I find it quite trivial to use (not that I have to maintain large chunks of systems anyways). But I see the benefit of masking, unmasking, enabling and disabling multiple services by just one underlaying "thing", rather than messing around with dozens of scripts. Even if there are pros and cons.
Same is valid for letting go mplayer in favor to mpv (after all the years, since mplayer has shown up).
Maybe I can see myself getting along with flatpaks one day. But then, people and changes are always a difficult thing. Let's first see how the overall acceptance within the Linux community is. Right now it still looks quite controversal to me.
Comment