Linked by Amjith Ramanujam on Tue 23rd Dec 2008 00:30 UTC
Linux A next-generation package manager called Nix provides a simple distribution-independent method for deploying a binary or source package on different flavours of Linux, including Ubuntu, Debian, SUSE, Fedora, and Red Hat. Even better, Nix does not interfere with existing package managers. Unlike existing package managers, Nix allows different versions of software to live side by side, and permits sane rollbacks of software upgrades.
Thread beginning with comment 341184
To read all comments associated with this story, please click here.
Comment by Netfun81
by Netfun81 on Tue 23rd Dec 2008 05:33 UTC
Netfun81
Member since:
2008-03-25

I would love to one day have a single package management system for Linux. It would make it so much easier for developers of applications to not have to re-package to a deb, rpm, yum, etc. Its frustrating when downloading a program that isnt in your distribution repository and it only comes in some packages and not the one you need. Linux needs something like windows .exe file. Something that can be loaded on any distribution without compiling. Look how this works when downloading the adobe flash plugin from their site. They have tried to accommodate various distributions, but it's far from being user friendly.

Reply Score: 2

RE: Comment by Netfun81
by leetgeezer on Tue 23rd Dec 2008 09:29 in reply to "Comment by Netfun81"
leetgeezer Member since:
2008-11-02

Agreed totally on that one... the sad thing is that this ain't gonna happen soon; one guy will rant about how he has "no problems" under Ubuntu, other will say "stick to RPM" etc. What I dream of is an unified package manager with community managed sites... from which I could install e.g. LATEST VERSION of Boost without no problems.

Reply Parent Score: 1

RE[2]: Comment by Netfun81
by AdamW on Tue 23rd Dec 2008 09:32 in reply to "RE: Comment by Netfun81"
AdamW Member since:
2005-07-06

"from which I could install e.g. LATEST VERSION of Boost without no problems."

boost is a *library*. its releases are *not API compatible*. this means that when it gets updated, all the applications that build against it need to be rebuilt, and possibly patched for API changes.

the alternative, which is what this kind of scheme would require, is that every single app that's built against boost includes its own private copy of boost. and if you wanted to go from boost 1.36 to boost 1.37 you'd have to change every single app to include a copy of boost 1.37 rather than 1.36, and the rebuild would take five times longer because you'd be rebuilding boost itself in every single one. and if you loaded two apps which both used boost, you'd get two copies of boost loaded into memory. or, five, if you used five apps.

this is the kind of thing I mean when I say people don't know what the hell they're talking about.

Reply Parent Score: 4