From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Recent change in 'guix package --search-paths' behavior?
Date: Thu, 11 May 2017 10:33:47 +0200 [thread overview]
Message-ID: <87a86jx05w.fsf@gnu.org> (raw)
In-Reply-To: <87lgq3eus9.fsf@gmail.com> (Chris Marusich's message of "Thu, 11 May 2017 00:07:18 -0700")
Hi Chris,
Chris Marusich <cmmarusich@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Chris Marusich <cmmarusich@gmail.com> skribis:
>>
>>> Hi,
>>>
>>> The manual says ((guix) Invoking guix package):
>>>
>>> This option can also be used to compute the _combined_ search paths
>>> of several profiles. Consider this example:
>>>
>>> $ guix package -p foo -i guile
>>> $ guix package -p bar -i guile-json
>>> $ guix package -p foo -p bar --search-paths
>>>
>>> The last command above reports about the ‘GUILE_LOAD_PATH’
>>> variable, even though, taken individually, neither ‘foo’ nor ‘bar’
>>> would lead to that recommendation.
>>
>> [...]
>>
>>> Is the documentation wrong, or is this a regression?
>>
>> Try with “guile2.2-json” instead of “guile-json”.
>>
>> Ludo’.
>
> As usual, you're right! :-) That worked:
[...]
> Why does 'guix' resolve to guile@2.2.2, but 'guile-json' resolves to
> guile-json@0.6.0?
It’s because we’re not done with the transition:
https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00436.html
The idea is to incrementally rename all “guile2.2-foo” packages to
“guile-foo”, and, when needed, keep an extra “guile2.0-foo”. For
guile-json this hasn’t been done yet, but now’s probably a good time to
do it.
> Is it because, as mentioned in the comments in procedure
> 'find-newest-available-packages' in gnu/packages.scm, "the preferred
> package is whichever one was found last by 'fold-packages'"?
>
> I've attached a patch for the documentation which might help clarify
> this for anyone who has the same question in the future. What do you
> think? Too much detail for an edge case, or a useful footnote?
I would rather not add more text to it because the example will become
valid again soonish, and the extra text might muddy waters.
WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-05-11 8:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 8:45 Recent change in 'guix package --search-paths' behavior? Chris Marusich
2017-05-10 12:08 ` Ludovic Courtès
2017-05-11 7:07 ` Chris Marusich
2017-05-11 8:33 ` Ludovic Courtès [this message]
2017-05-11 8:46 ` Chris Marusich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a86jx05w.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.