GNU bug report logs - #34590
Effects of GUIX_PACKAGE_PATH and --load-path differ

Previous Next

Full log

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Daniel Gerber <dg <at> atufi.org>
To: bug-guix <at> gnu.org
Subject: Effects of GUIX_PACKAGE_PATH and --load-path differ
Date: Wed, 20 Feb 2019 11:38:19 +0100

Hi,

From reading the doc on `guix environment`:

-L, --load-path=DIR    prepend DIR to the package module search 
path

I would expect these to be exactly equivalent:

$ export GUIX_PACKAGE_PATH=; guix environment -L path ...
$ export GUIX_PACKAGE_PATH=path; guix environment ...

Yet they differ. With libuv <at> 1.24.0 in the guix channel (a37bdf4) 
and libuv <at> 1.26.0 in --and also node <at> 11.10.0 only in-- 
/gnu/guix-local-packages/:

$ export GUIX_PACKAGE_PATH=/gnu/guix-local-packages/; guix 
environment --no-grafts -C node <at> 11.10.0 --ad-hoc strace gdb -- ls 
/gnu/store/ |grep -o libuv-.*
libuv-1.26.0

$ export GUIX_PACKAGE_PATH=; guix environment -L 
/gnu/guix-local-packages/ --no-grafts -C node <at> 11.10.0 --ad-hoc 
strace gdb -- ls /gnu/store/ |grep -o libuv-.*
libuv-1.24.0

Is this the intended behaviour?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.