This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

Nix fixes dependency hell on all Linux distributions

Posted by: Anonymous [ip: 78.32.219.25] on December 22, 2008 08:22 PM
This is just completely stupid. Debian hasn't had "Dependency hell" since apt was created. That's around the start of most of my time with Linux, which something like over 14 years now. If people want to keep using RPM or some similar package tool, getting dependency hell, and then reinventing the wheel, that's their problem. As far as debian-and-derivative users are concerned, the issue doesn't exist, and so we're hardly going to be convinced by solutions to something that doesn't need fixed.

As for installing different libs with every package... that's insane. It amounts to installing a xen virtual server for every package, which no one in their right mind considers viable for a simple desktop machine with potentially thousands of programs installed (yes, on debian, easily, I know redhat users are more limited ;). Creating a new OS install for each program is hardly a solution. Also, again, with debian, the few rare problems that this MIGHT fix are easily solved.

What we REALLY need is a package manager like debian's in every way, except for:

a) Package manager gateways for closed systems like cpan, ctan, pear, etc.

b) Standardised, network-wide deployment and configuration (including hierarchical config and lockdown for EVERY tool/app on the system) by policies set in a directory like LDAP.

c) Highly integrated next-generation security policy tools like SELinux or AppArmor (installing policies when a package is installed, etc.)

d) Auto-choosing and configuration of packages by FEATURES, not name. So if I say I want to use a database with object-orientation and a python dbapi interface, having previously said I want smtp mail services, it should uninstall mysql, install postgresql, uninstall my mailserver that doesn't support postgresql, install a mailserver that does use it, and configure it using the abstracted mail config I set in the network directory.

e) and, well, a few more things too. But god... stop solving things that are already solved, and work on a next-gen distro please. I mean, I'd be happy with even a distro that had decent package management and encouraged network-wide PKI (with your mailserver setup, database server setup, ssh setup, etc.) as standard.

#

Return to Nix fixes dependency hell on all Linux distributions