From: "Ludovic Courtès" <ludo@gnu.org>
To: Daniel Gerber <dg@atufi.org>
Cc: 34590@debbugs.gnu.org
Subject: bug#34590: Effects of GUIX_PACKAGE_PATH and --load-path differ
Date: Wed, 06 Mar 2019 14:38:11 +0100 [thread overview]
Message-ID: <87lg1si0n0.fsf@gnu.org> (raw)
In-Reply-To: <8736oivj6s.fsf@atufi.org> (Daniel Gerber's message of "Wed, 20 Feb 2019 11:38:19 +0100")
Hi Daniel,
Daniel Gerber <dg@atufi.org> skribis:
> 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@1.24.0 in the guix channel (a37bdf4) and libuv@1.26.0 in --and also node@11.10.0 only in--
> /gnu/guix-local-packages/:
>
> $ export GUIX_PACKAGE_PATH=/gnu/guix-local-packages/; guix environment
> --no-grafts -C node@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@11.10.0 --ad-hoc strace
> gdb -- ls /gnu/store/ |grep -o libuv-.*
> libuv-1.24.0
>
> Is this the intended behaviour?
Probably not.
I experimented a bit and couldn’t find any evidence that the search path
order would differ.
However, what do /gnu/guix-local-packages/ contain? I suppose it
provides node@11.10.0?
Then my guess is that “node@11.10.0” is ambiguous and that
‘specification->package’ chooses one of the two in a non-deterministic
fashion.
Can you show the output of:
guix package -A node
guix package -A node -L /gnu/guix-local-packages
GUIX_PACKAGE_PATH=/gnu/guix-local-packages guix package -A node
?
TIA,
Ludo’.
next prev parent reply other threads:[~2019-03-06 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 10:38 bug#34590: Effects of GUIX_PACKAGE_PATH and --load-path differ Daniel Gerber
2019-03-06 13:38 ` Ludovic Courtès [this message]
2019-03-06 14:43 ` Daniel Gerber
2019-03-06 17:49 ` Ludovic Courtès
2019-03-07 8:01 ` Daniel Gerber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lg1si0n0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=34590@debbugs.gnu.org \
--cc=dg@atufi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).