From: "Ludovic Courtès" <ludo@gnu.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: 44327@debbugs.gnu.org
Subject: bug#44327: `guix install` doesn't warn about collison in profile
Date: Wed, 04 Nov 2020 18:15:48 +0100 [thread overview]
Message-ID: <87o8kd6o1n.fsf@gnu.org> (raw)
In-Reply-To: <86blgdao67.fsf@163.com> (Zhu Zihao's message of "Wed, 04 Nov 2020 09:47:12 +0800")
Zhu Zihao <all_but_last@163.com> skribis:
>> > I also suggest to raise an error when conflict detected during building
>> > profile to force user to resolve it.
>
>> It should be already the case. :-)
>
> IIRC the deafult collision handler of union-build is
> warn-about-collision which doesn't terminate the build when collision
> occured.
We’re talking about different things. Whatever happens during
‘union-build’ happens too late and won’t lead to user-friendly errors.
I was referring to the mechanism implemented a while back and submitted
here:
https://issues.guix.gnu.org/27271
> BTW, There's something called "priority" in Nix. The package with higher
> priority in manifest will be able to override the package with lower one.
My experience with it (from 8+ years ago, though) is that it was
inconvenient and not natural—as a user you don’t want to ask yourself
which package should have the highest priority, you just want to have
these things installed.
The approach we took is to error out, with a clear diagnostic, when Guix
knows beforehand that two packages cannot coexist in the same profile.
Thanks,
Ludo’.
prev parent reply other threads:[~2020-11-04 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 11:17 bug#44327: `guix install` doesn't warn about collison in profile Zhu Zihao
2020-10-30 16:15 ` zimoun
2020-10-30 16:18 ` Ludovic Courtès
2020-10-30 16:30 ` zimoun
2020-10-31 10:31 ` Ludovic Courtès
2020-11-04 1:47 ` Zhu Zihao
2020-11-04 17:15 ` Ludovic Courtès [this message]
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=87o8kd6o1n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44327@debbugs.gnu.org \
--cc=all_but_last@163.com \
/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).