Hi,
> I am trying to prepare guix for installing at non-root location. I have
> followed the documentation available here:
> https://github.com/pjotrp/guix-notes/blob/master/INSTALL.org#error-in-procedure-scm-error-no-code-for-module-gcrypt-hash
I’d just like to note that this is not official documentation of the
Guix project. I don’t know if this is still accurate information.
I understand that this is not an official documentation. I installed guix through office documentation on my system. It is working fine.
Do you want to build everything from source on your system or do you
prefer to use binaries from the Guix project’s build farms? Do you have
access to user namespaces / can you use “unshare” for file system
shenanigans?
I need to build guix for non-root location because at several places its hard to convince to use such system. However, I need several packages which are not usually available or outdated. The guix projects allows me to do so. To accomplish that I need truly non-root permission oriented method to bootstrap and install whatever I deem necessary for my use case. Unfortunately, I am stuck at Centos6 which uses old kernel 2.6.32-696.el6.x86_64. I am able to install nix on this system at non-root location. It works fine but NIx community has decided to use 2.0 which only works on newer kernel. Therefore, I have to now backport several packages. Making it really hard because lot of packages are broken. Its manageable but not ideal. Whereas the guix seems to be independent of kernel (atleast that is my assumption so far).
> ./pre-inst-env guix package -i guix
We don’t recommend using Guix from a git checkout in most cases, because…
> substitute: ERROR: In procedure scm-error:
> substitute: no code for module (gcrypt hash)
I understand but that is why my personal work machine (running Ubuntu 18.04) is using the 1.0.0 guix not the latest git repo one. Also, I am boostraping guix/gnu store from tag v1.0.0.
…you would need to take care of providing the appropriate Guile
environment all by yourself whereas “guix pull” does all of this for
you. This error tells you that guile-gcrypt is not available in the
environment in which the daemon runs.
This is the place where I am struggling. I am not sure what more do I need to do then described in pjotrp notes. I could not find anything specific in the guix documentation as well to accomplish this.
I would also like to suggest an alternative to a root-less installation.
At the HPC cluster where I work we run the guix-daemon as root on a
virtual machine where /gnu/store is a writable NFS share. Every machine
that uses Guix only needs to mount this share as read-only.
This option is not available as I stated earlier, I do not have the root permission.
--
Ricardo
--Rohit