From: Vincent Legoll <vincent.legoll@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH RFC 0/4] Getting rid of input labels?
Date: Thu, 20 May 2021 18:19:11 +0200 [thread overview]
Message-ID: <CAEwRq=o4G+346w109-1O682cJnexHTHdHNrUWP7K_50KfykYbA@mail.gmail.com> (raw)
In-Reply-To: <20210520145830.14108-1-ludo@gnu.org>
Hello,
On Thu, May 20, 2021 at 5:03 PM Ludovic Courtès <ludo@gnu.org> wrote:
> Instead of writing:
>
> (native-inputs
> `(("autoconf" ,autoconf)
> ("automake" ,automake)
> ("pkg-config" ,pkg-config)
> ("guile" ,guile-3.0)))
>
> one can write:
>
> (native-inputs (list autoconf automake pkg-config guile-3.0))
What about
> (native-inputs
> `(,autoconf
> ("truc" ,muche)
> "pkg-config"
> ))
i.e. allowing package objects, tuples and names, and it would DTRT ?
Wouldn't something like that be possible ?
--
Vincent Legoll
next prev parent reply other threads:[~2021-05-20 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 14:58 [PATCH RFC 0/4] Getting rid of input labels? Ludovic Courtès
2021-05-20 14:58 ` [PATCH RFC 1/4] records: Support field sanitizers Ludovic Courtès
2021-05-20 14:58 ` [PATCH RFC 2/4] DRAFT packages: Allow inputs to be plain package lists Ludovic Courtès
2021-05-20 14:58 ` [PATCH RFC 3/4] DRAFT gnu: Change inputs of core packages to plain lists Ludovic Courtès
2021-05-20 14:58 ` [PATCH RFC 4/4] DRAFT lint: Add 'input-labels' checker Ludovic Courtès
2021-05-20 16:19 ` Vincent Legoll [this message]
2021-05-26 13:35 ` [PATCH RFC 0/4] Getting rid of input labels? Ludovic Courtès
2021-05-20 19:31 ` Maxime Devos
2021-05-26 13:43 ` Ludovic Courtès
2021-05-27 19:02 ` Maxime Devos
2021-05-21 15:35 ` Nicolas Goaziou
2021-05-26 14:02 ` Ludovic Courtès
2021-05-30 16:23 ` Ryan Prior
2021-06-08 13:05 ` Ludovic Courtès
2021-06-10 21:39 ` 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
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='CAEwRq=o4G+346w109-1O682cJnexHTHdHNrUWP7K_50KfykYbA@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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).