On 10/03/16 18:44, Ricardo Wurmus wrote:
Instead of “guix pull” may I suggest using git instead? Especially,
when you have multiple machines on which Guix should run, it may make
sense to just clone the Guix git repository once from the Internet,
clone it to the other machines via local network, and then update once
in a while via “git pull” (not “guix pull”).
You can create a link “~/.config/guix/latest” pointing to, say,
“~/dev/guix” (if that’s the directory holding the cloned repository).
When you update with “git pull” you’ll only have to download recent
changes, not the whole Guix code.
Does this make sense?
It's a good start for sure, thx! However, I now get loads of
;;; note: source file /home/zwets/.config/guix/latest/gnu/packages/{...}.scm
;;; newer than compiled
/gnu/store/3lg5c1nidbj0kjdz5b63hn3vp29kzf0s-guix-0.9.0.c3f29bc/share/guile/site/2.0/gnu/packages/{...}.go
whenever I run guix. Do I need to build the pulled source,
then point my guix command elsewhere?
My `which guix` is /usr/local/bin/guix pointing at
/var/guix/profiles/per-user/root/guix-profile/bin/guix,
the way the installation instructions suggest.
Cheers
Marco
