From: Simon Tournier <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>,
Tobias Geerinckx-Rice <me@tobias.gr>,
guix-devel@gnu.org
Subject: Re: Rebuilding a package after removing a build step
Date: Fri, 20 Sep 2024 19:10:34 +0200 [thread overview]
Message-ID: <877cb6s12t.fsf@gmail.com> (raw)
In-Reply-To: <m1cyl1z7hj.fsf@fastmail.net>
Hi Konrad,
On mer., 18 sept. 2024 at 10:33, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> Unfortunately, when there are several packages with identical name and
> version number in two channels, Guix silently chooses one of them.
Choose when doing what? :-)
When running “guix shell” or “guix package”, it should warn. It
doesn’t? Ah? I thought it does… Hum?
When packaging, you choose: you use one module or the other, or both.
Guile tells you if there is a symbol clash, so then you resolve it by
using some #:prefix or #:hide at #:use-module. Else you choose one
symbol or the other inside the package definition.
Cheers,
simon
next prev parent reply other threads:[~2024-09-20 17:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 15:59 Rebuilding a package after removing a build step Konrad Hinsen
2024-09-17 16:27 ` Tobias Geerinckx-Rice
2024-09-18 8:33 ` Konrad Hinsen
2024-09-18 17:40 ` Suhail Singh
2024-09-18 18:27 ` Konrad Hinsen
2024-09-19 15:32 ` Suhail Singh
2024-09-20 17:10 ` Simon Tournier [this message]
2024-09-22 8:34 ` Konrad Hinsen
2024-09-22 16:48 ` Kaelyn
2024-09-23 8:22 ` Konrad Hinsen
2024-09-23 8:42 ` Andreas Enge
2024-09-23 15:29 ` Konrad Hinsen
2024-09-23 16:03 ` Vagrant Cascadian
2024-09-23 18:17 ` Suhail Singh
2024-09-24 0:16 ` Kaelyn
2024-09-24 5:24 ` Konrad Hinsen
2024-09-23 16:27 ` Tobias Geerinckx-Rice
2024-09-26 13:35 ` Ludovic Courtès
2024-09-30 14:25 ` Konrad Hinsen
2024-09-18 19:32 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
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=877cb6s12t.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=me@tobias.gr \
/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).