2019 LinuxQuestions.org Members Choice AwardsThis forum is for the 2019 LinuxQuestions.org Members Choice Awards.
You can now vote for your favorite projects/products of 2019. This is your chance to be heard! Voting ends on February 12th.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
View Poll Results: Universal Packaging Format of the Year
None of the above should have been an option as well as .deb, .rpm, or source etc...
Perhaps it would be better to add "Universal" to the title? Universald packaging format of the year? That would preclude .deb & .rpm then.
Source isn't a packaging format per se, since ALL packages are at some point derived from source, and you cannot simply INSTALL from source without compiling first. So it shouldn't be included anyway.
Last edited by Timothy Miller; 01-02-2020 at 09:00 PM.
Actually I was thinking about a dockerized (or containerized) packaging format, but it is not yet "invented". Probably in the future....
To be fair, both Snap and Flatpak AIM to be similar to a containerized (being sandboxed) format, and it can work just fine as such if the people packaging do it correctly (from what I understand) on at least flatpak. I personally dislike snap so not as certain that snap in and of itself is ready for that, but probably is.
Apt is 'universal' over all the distros that I use.
TBH, 'apt' ain't a 'packaging format. It's a package management format. Slight difference.
.deb or .rpm are not 'universal', either. Those that require .debs won't install .rpms without some form of conversion. And vice-versa. The fact that the actual content of both is identical is neither here nor there.....it's the package-management 'specifics' that set them apart for most folks.
The title, as it stands, is correct, for the choices given. Every one of those three is intended to be a 'universal' format in the sense that you can run them on any OS, regardless of which camp it belongs to.
But Snaps are heavily promoted by Canonical. FlatPak is, I believe, developed more on the Red Hat side of things. So - given that the Sherlock Holmes theory holds water here; after process of elimination, whatever is left over at the very end MUST be the true facts of the case (however 'fantastic') - this really only leaves the AppImage as the one, truly 'universal' packaging format.
Sorry if y'all don't like my logic.
Quote:
Originally Posted by ondoho
Universal:
Code:
./configure; make; install
Mm-hm. Oh, it's 'universal' right enough.....but it still ain't a 'packaging' format, is it? More of a 'play on words', I should have said...
Mike.
Last edited by Mike_Walsh; 01-06-2020 at 10:05 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.