From: Greg Hogan <code@greghogan.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Order of manifest and overlapping binaries
Date: Tue, 16 May 2023 16:41:34 -0400 [thread overview]
Message-ID: <CA+3U0ZmuH9d7jjbYb5CVrBgvZExrPCBgOH-Z6oPjRE3yj_0KDg@mail.gmail.com> (raw)
I could not find documentation on this circumstance or how to resolve.
Both 'parallel' and 'moreutils' produce a 'bin/parallel' and only one
can go in the $GUIX_PROFILE.
Creating a container, the latter package overshadows the former
package, as below. Unclear if this is consistent. In my manifest the
former package overshadows the latter (I'd prefer to have parallel's
parallel, but by default I have sorted the listing alphabetically). Is
there a better way to fix this?
Greg
--8<---------------cut here---------------start------------->8---
$ guix shell --container moreutils parallel which coreutils
[env]$ readlink -f `which parallel`
/gnu/store/xd9kbadmrrbpkjs9vl1v9rhgayfxwgbc-parallel-20230422/bin/parallel
guix shell --container parallel moreutils which coreutils
[env]$ readlink -f $(which parallel)
/gnu/store/60zdm9zm0nqm5d97vs30sf4plb2ib5p9-moreutils-0.67/bin/parallel
--8<---------------cut here---------------end--------------->8---
This is operating from a recent guix pull:
--8<---------------cut here---------------start------------->8---
$ guix describe
Generation 44 May 11 2023 17:02:53 (current)
guix d6f6b57
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: d6f6b57766e95d2fa8af63d4460a2b303ca4d867
--8<---------------cut here---------------end--------------->8---
next reply other threads:[~2023-05-16 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 20:41 Greg Hogan [this message]
2023-05-16 20:51 ` Order of manifest and overlapping binaries Csepp
2023-10-23 13:18 ` Greg Hogan
2023-10-23 14:39 ` Kaelyn
2023-10-31 17:29 ` Greg Hogan
2023-05-16 21:23 ` Attila Lendvai
2023-05-25 3:32 ` John Kehayias
2023-10-23 18:20 ` Simon Tournier
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=CA+3U0ZmuH9d7jjbYb5CVrBgvZExrPCBgOH-Z6oPjRE3yj_0KDg@mail.gmail.com \
--to=code@greghogan.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 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).