<taylan>programs often depend on other software being installed on your machine. for example Firefox might require a PNG image decoding library, otherwise it couldn't display PNG images. a package manager manages the installation of such dependencies automatically. this is perhaps one of the most important features of an operating system distribution.
<taylan>Guix handles dependencies in a special way that ties them together strongly with the package they belong to, so for example when libpng is updated, a new Firefox package is also built, so that one can test them separately, roll back to the other Firefox (that uses the previous libpng version) etc. seamlessly
<taylan>GuixSD is still alpha or beta stage software, and maybe at its 1.0 release it will still be for somewhat advanced users, but I'd say that the concepts underlying it could be hidden from the user just fine
<h0wl3vvd>my parabola X's get crashed after x updated cuz something was not supported on my machine
<rekado>HeisenbergsDog: if you want to keep your packages separate from Guix upstream for some reason you can just collect them in a repository of your own and add the location to your GUIX_PACKAGE_PATH.
<rekado>but it's probably better to just submit a patch to the mailing list.
<piyo>Oh, I was struggling with getting emacs+guix up and running but I succeeded when redoing the emacs-initial-setup. :-) Well I made the mistake of using the "hacking way" code sample when I am using the binary installation in Debian Jessie.
<piyo>Not (setq guix-load-path ...) seems to be correct for my case.
<davexunit>sweet, I have made the nginx service extensible