From: Mekeor Melire <mekeor@posteo.de>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 67292@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: bug#67292: emacs / emacs-transient collisions and bundling
Date: Tue, 28 Nov 2023 11:12:40 +0000 [thread overview]
Message-ID: <87edgajfim.fsf@posteo.de> (raw)
In-Reply-To: <55357bdc-cdfe-c264-7618-f69681565fb6@telenet.be>
2023-11-28 01:58 maximedevos@telenet.be:
> [[PGP Signed Part:Undecided]]
> Op 23-11-2023 om 15:17 schreef Mekeor Melire:
> >> >> Bug 2: no collision handling.
> > As far as I know, Guix does not provide a facility to
> > prioritize a
> > file from one package over the same file from another package.
>
> As I mentioned in a previous e-mail in #67292, it does provide a
> facility -- not mentioned: by default, the first package in the
> list
> is prioritized.
Sorry for the oversight. Which list are you referring to?
> If the collision is not a problem then Guix shouldn't be warning
> about
> it -- as such, the collision handling needs to be adjusted to
> not emit
> a warning in this case.
True. That'd be nice. Should we discuss this here, in this bug-report or in another, new bug-report that is dedicated to the problem of unnecessary collision-warnings?
prev parent reply other threads:[~2023-11-28 11:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 22:44 bug#67292: emacs / emacs-transient collisions and bundling Maxime Devos
2023-11-20 10:22 ` Simon Tournier
2023-11-20 12:39 ` Maxime Devos
2023-11-20 12:42 ` Maxime Devos
2023-11-20 13:46 ` Simon Tournier
2023-11-21 18:01 ` Maxime Devos
2023-11-22 20:53 ` Simon Tournier
2023-11-28 1:47 ` Maxime Devos
2023-11-28 9:45 ` Simon Tournier
2023-11-28 11:15 ` Mekeor Melire
2023-11-23 14:17 ` Mekeor Melire
2023-11-28 0:58 ` Maxime Devos
2023-11-28 11:12 ` Mekeor Melire [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edgajfim.fsf@posteo.de \
--to=mekeor@posteo.de \
--cc=67292@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
--cc=zimon.toutoune@gmail.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 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.