From: Josselin Poiret <dev@jpoiret.xyz>
To: "Greg Hogan" <code@greghogan.com>, "Ludovic Courtès" <ludo@gnu.org>
Cc: Christopher Baines <mail@cbaines.net>,
Mathieu Othacehe <othacehe@gnu.org>,
Ricardo Wurmus <rekado@elephly.net>,
Simon Tournier <zimon.toutoune@gmail.com>,
Tobias Geerinckx-Rice <me@tobias.gr>,
guix-devel <guix-devel@gnu.org>
Subject: Re: [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages
Date: Sat, 24 Jun 2023 12:09:15 +0200 [thread overview]
Message-ID: <87edm1rx2s.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CA+3U0ZkfNDO1QM3ztqBtGoV1SWvCFkJKdXu9+GWg4fAfo05Nig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 475 bytes --]
Hi Greg,
Greg Hogan <code@greghogan.com> writes:
> This has broken, for example, building clang with a newer version of
> gcc using package-input-rewriting/spec. What do you think of adding a
> hidden? property to enable the old behavior?
Since you're mentioning package-input-rewriting/spec, I assume you're
doing this in Guile? If so, package-input-rewriting doesn't have that
same behavior, and still replaces hidden packages!
HTH,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-06-24 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 12:01 [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages Ludovic Courtès
2023-03-08 12:03 ` [bug#62047] [PATCH 1/2] packages: Use SRFI-71 instead of SRFI-11 Ludovic Courtès
2023-03-08 12:03 ` [bug#62047] [PATCH 2/2] packages: 'package-input-rewriting/spec' ignores hidden packages Ludovic Courtès
2023-03-10 11:49 ` [bug#62047] [PATCH 1/2] packages: Use SRFI-71 instead of SRFI-11 Simon Tournier
2023-03-10 16:46 ` Ludovic Courtès
2023-03-10 17:44 ` Simon Tournier
2023-03-09 20:15 ` [bug#62047] [PATCH 0/2] '--with-input' & co. no longer replace hidden packages Josselin Poiret via Guix-patches via
2023-06-22 17:25 ` Greg Hogan
2023-06-24 10:09 ` Josselin Poiret [this message]
2023-09-14 15:41 ` Ludovic Courtès
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=87edm1rx2s.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=code@greghogan.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@cbaines.net \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--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.