On Sonntag, 19. August 2018 22:41:30 CEST you wrote: > It depends on how haunt package definition is written. Because of how guix > works, you can use a program that uses guile without having 'guile' command > available. Similarly, it makes it possible to run two programs at the same > time that depends on different versions of the same library.. that's something > that is very difficult to do outside guix and nix. It's one of the consequences > of packaging is done. This leads to the point that in theory, you SHOULD never > install _libraries_ in your user profile ie. the regular / default profile because > no executable will use it. Default guix profile, SHOULD, I THINK, only > contain data and executables. I see. So if I want to work on some software that uses a particular library I could install that library into a custom profile, enter that profile and do my work.
> That is not a good example use of hacking on a guile project because > guix is using > it's own version of guile which might be different from the version of > guile you > installed in your profile... again because functional packaging. If you > want to > hack on guix follow the README that you can find in guix git repository > at [1] > > [1] git clone https://git.savannah.gnu.org/git/guix.git I did not know that Guix includes its own Guile, I thought it used the Guile that's on the system.