From: Attila Lendvai <attila@lendvai.name>
To: Greg Hogan <code@greghogan.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Order of manifest and overlapping binaries
Date: Tue, 16 May 2023 21:23:43 +0000 [thread overview]
Message-ID: <lckDqawSs66VF196-j6UjszMZyXedKpB1-1MoOC0OGWkiqpJVeSxmmzDkpOoy2yk8lsMGab_kvqQ2io7PkaJeUqYCfwOvrMp_RZ3ou0tVEI=@lendvai.name> (raw)
In-Reply-To: <CA+3U0ZmuH9d7jjbYb5CVrBgvZExrPCBgOH-Z6oPjRE3yj_0KDg@mail.gmail.com>
> 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.
i have proposed a solution for a special case of this problem: to do alphanumeric sorting, which together with semantic versioning picks the latest from the collisions of different versions of the same package.
see: https://issues.guix.gnu.org/50878#12
the cleanup commits reached master by now, but the actual change of the semantics of the union has not. it needs to be revived/rebased.
in its current form it wouldn't help in your case, but it points to the relevant part of the codebase.
HTH,
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“In a country where the sole employer is the State, opposition means death by slow starvation. The old principle: who does not work does not eat, has been replaced by a new one: who does not obey shall not eat.”
— Leon Trotsky
next prev parent reply other threads:[~2023-05-16 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 20:41 Order of manifest and overlapping binaries Greg Hogan
2023-05-16 20:51 ` 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 [this message]
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='lckDqawSs66VF196-j6UjszMZyXedKpB1-1MoOC0OGWkiqpJVeSxmmzDkpOoy2yk8lsMGab_kvqQ2io7PkaJeUqYCfwOvrMp_RZ3ou0tVEI=@lendvai.name' \
--to=attila@lendvai.name \
--cc=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).