> it’s not a bootable distribution yet, but rather one to be installed on top of a running GNU/Linux system. For a moment there I thought the GNU Hurd had been finished, I misread it as GNU Unix :(
Introducing GNU Guix
11–20 of 113 posts
Re: Introducing GNU Guix
#12Re: Introducing GNU Guix
#13Because the existing fragmentation of GNU package management is too confusing, so we need a new standard for everyone to rally round.
Re: Introducing GNU Guix
#14* Why utilize scheme? It's declaritive utilize a markup like yaml, don't go off the deep end because you can.
* Utilize OS specific features such as jails, bind mounts, namespaces, you can have the same NIX style separation without destroying FHS.
* Parse the config files for options, it's easy cmake, autocrap, etc all have parsable formatting this way you don't need to mess with adding build time options.
* Parse the source for dependencies, there are lots of white papers of people doing this and beating human made spec files.
* Utilize machine learning for classification of options, dependency resolution (utilizing previous data).
Re: Introducing GNU Guix
#15What problem does it solve?
Re: Introducing GNU Guix
#16> unprivileged package management
seems quite, well, useless imho. If on the other hand everything in guix lives in the userland, I can see myself using it in the servers I don't have root-access to..
Re: Introducing GNU Guix
#17What problem does it solve?
For me, some of its features, specially non-privileged user package management, are interesting. I'm not so much interested in the distribution at the moment, more in the package manager. I imagine there aren't many supported packages yet, so it's a matter of writing scripts... eventually it can become a distribution. Not for everyone.
But I still see no problem in more package managers being out there - any one has a problem with yum / apt being two different package managers? Why is yet another package manager is a bad thing?
Re: Introducing GNU Guix
#18Can someone explain what benefits do I get for using this rather than the package manager offered by my distribution? And do you need root access to install guix? Because if you do then > unprivileged package management seems quite, well, useless imho. If on the other hand everything in guix lives in the userland, I can see myself using it in the servers I don't have root-access to..
Re: Introducing GNU Guix
#19What problem does it solve?
from a theoretical, conceptual view point, nix is the holy grail in package management.
Re: Introducing GNU Guix
#20Debian's dpkg and apt are both GPL2+. What's the reason they are reinventing the wheel here? Is there some kind of licence incompatibility that the GNU project cares about? Is there some kind of major architectural difference? Why is it important enough to fragment Free Software developers over? I feel that this should be answered in an FAQ, but I can't find the answer anywhere.
From the e-mail: In addition to standard package management features, Guix supports transactional upgrades and roll-backs, unprivileged package management, per-user profiles, and garbage collection Maybe that’s enough? (I don’t understand package managers.)