From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: new manifest format readers?
Date: Sun, 11 Jun 2017 23:16:32 +0200 [thread overview]
Message-ID: <8737b6p6mn.fsf@gnu.org> (raw)
In-Reply-To: <87tw3mr0kc.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 11 Jun 2017 17:44:35 +0200")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>>
>>> Ricardo Wurmus writes:
>>
>> [...]
>>
>>>> ;; Boilerplate code to turn the above list of packages into a manifest
>>>> (use-modules (gnu packages))
>>>> (packages->manifest (map (compose list specification->package+output) packages))
>>>
>>> Yes, I finally found this and it is not very friendly/discoverable.
>>
>> Agreed. How about making these two changes:
>>
>> 1. Include (gnu packages) in the default evaluation environment of
>> manifests.
>>
>> 2. (define (package-specifications->manifest specs)
>> (packages->manifest (map (compose list specification->package+output)
>> specs)))
>>
>> Thoughts?
>
> This sounds like a very useful improvement to me.
Done in c08ea55e7ec25261e4596bf6726a83c1ed056b94.
In fact #1 was already implemented.
Ludo’.
next prev parent reply other threads:[~2017-06-11 21:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 12:03 new manifest format readers? Ricardo Wurmus
2017-06-09 13:09 ` Mathieu Othacehe
2017-06-09 13:56 ` Ludovic Courtès
2017-06-09 13:58 ` Jan Nieuwenhuizen
2017-06-09 14:58 ` Ricardo Wurmus
2017-06-10 2:06 ` Arun Isaac
2017-06-11 14:15 ` Ludovic Courtès
2017-06-11 15:44 ` Ricardo Wurmus
2017-06-11 21:16 ` Ludovic Courtès [this message]
2017-06-12 3:56 ` Jan Nieuwenhuizen
2017-06-12 8:31 ` Chris Marusich
2017-06-09 15:08 ` Björn Höfling
2017-06-09 18:12 ` Ricardo Wurmus
2017-06-10 17:19 ` myglc2
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=8737b6p6mn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).