From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Ulf Herrman <striness@tilde.club>
Cc: dev@jpoiret.xyz, zimon.toutoune@gmail.com, othacehe@gnu.org,
ludo@gnu.org, me@tobias.gr, 65665@debbugs.gnu.org,
rekado@elephly.net, guix@cbaines.net
Subject: bug#65665: [PATCH] Really get all the implicit inputs.
Date: Thu, 05 Oct 2023 22:36:42 -0400 [thread overview]
Message-ID: <87a5swlbnp.fsf@gmail.com> (raw)
In-Reply-To: <87msxmqwng.fsf@tilde.club> (Ulf Herrman's message of "Sat, 16 Sep 2023 04:45:23 -0500")
Hello Ulf!
Ulf Herrman <striness@tilde.club> writes:
> This patch series causes package-mapping to recurse into package and bag
> arguments when #:deep? #t is given. It also recurses into gexps and
> gexp inputs in search of packages to devour. It also ensures that build
> systems leave all of their implicit package arguments in the bag
> arguments, ready to be found by package-mapping. It also fixes a couple
> build system errors I came across while modifying 40+ build systems and
> testing a deep package transformation.
Nice series!
I've reviewed it, and it makes sense to me. I'd like to apply it to the
core-updates branch. Core team, what say you?
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-06 3:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 20:14 bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs Ulf Herrman
2023-09-01 18:08 ` Csepp
2023-09-03 13:02 ` Maxim Cournoyer
2023-09-05 14:57 ` Simon Tournier
2023-09-16 9:45 ` bug#65665: [PATCH] Really " Ulf Herrman
2023-10-06 2:36 ` Maxim Cournoyer [this message]
2023-10-06 7:37 ` Ulf Herrman
2023-10-07 3:47 ` Ulf Herrman
2023-10-12 13:47 ` bug#65665: package-mapping with #:deep? #t doesn't " Ludovic Courtès
2023-10-12 7:07 ` bug#65665: [PATCH] Really " Ludovic Courtès
2023-10-12 14:22 ` Simon Tournier
2023-10-12 14:06 ` bug#65665: package-mapping with #:deep? #t doesn't " Ludovic Courtès
2023-10-12 16:00 ` Maxim Cournoyer
2023-10-14 14:47 ` Ludovic Courtès
2023-10-13 3:11 ` Ulf Herrman
2023-10-14 15:18 ` Ludovic Courtès
2023-10-15 7:12 ` Ulf Herrman
2023-10-21 14:31 ` Ludovic Courtès
2023-10-21 22:22 ` Ulf Herrman
2023-10-23 13:53 ` Simon Tournier
2023-10-12 13:53 ` Ludovic Courtès
2023-10-12 15:53 ` Maxim Cournoyer
2023-10-13 1:49 ` Ulf Herrman
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=87a5swlbnp.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65665@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=guix@cbaines.net \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
--cc=othacehe@gnu.org \
--cc=rekado@elephly.net \
--cc=striness@tilde.club \
--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 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).