From: Simon Tournier <zimon.toutoune@gmail.com>
To: Ulf Herrman <striness@tilde.club>, 65665@debbugs.gnu.org
Subject: bug#65665: package-mapping with #:deep? #t doesn't get all the implicit inputs
Date: Tue, 05 Sep 2023 16:57:15 +0200 [thread overview]
Message-ID: <868r9ku0qc.fsf@gmail.com> (raw)
In-Reply-To: <87h6ofufy5.fsf@tilde.club>
Hi,
On Thu, 31 Aug 2023 at 15:14, Ulf Herrman <striness@tilde.club> wrote:
> I propose that we have the build system lower procedure (that is, the
> one that converts from package to bag) completely fill in the argument
> list with all defaults, and we modify build-system-with-package-mapping
> to transform all arguments that look like a package or a list of
> packages (or maybe even a tree containing packages).
On principle, this looks a good idea.
Do you already have an implementation? Because transformations lead to
headache and sometimes the implementation is hard, well evil, details
and all that. :-)
Cheers,
simon
next prev parent reply other threads:[~2023-09-05 16:07 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 [this message]
2023-09-16 9:45 ` bug#65665: [PATCH] Really " Ulf Herrman
2023-10-06 2:36 ` Maxim Cournoyer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868r9ku0qc.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=65665@debbugs.gnu.org \
--cc=striness@tilde.club \
/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.