all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: new manifest format readers?
Date: Sun, 11 Jun 2017 16:15:24 +0200	[thread overview]
Message-ID: <87tw3msj9f.fsf@gnu.org> (raw)
In-Reply-To: <87d1adw9eb.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Fri, 09 Jun 2017 15:58:04 +0200")

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?

(To be clear, my suggestion is to do this in addition to adding support
for a new format.)

Ludo’.

  parent reply	other threads:[~2017-06-11 14:15 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 [this message]
2017-06-11 15:44     ` Ricardo Wurmus
2017-06-11 21:16       ` Ludovic Courtès
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tw3msj9f.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=janneke@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 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.