From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Patches to implement system roll-back and switch-generation
Date: Wed, 19 Oct 2016 23:07:40 +0200 [thread overview]
Message-ID: <87y41k2gkj.fsf@gnu.org> (raw)
In-Reply-To: <87inssx0y4.fsf@gmail.com> (Chris Marusich's message of "Sat, 15 Oct 2016 23:28:03 -0700")
Hi Chris,
Chris Marusich <cmmarusich@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>> We can now avoid monadic procedures by using the declarative counterpart
>> of the monadic API. That is, we could write:
>>
>> (define (grub-configuration-file …) ;normal proc
>> (computed-file "grub.cfg" builder))
>>
>> instead of:
>>
>> (define (grub-configuration-file …) ;monadic proc
>> (gexp->derivation "grub.cfg" builder))
>>
>> I would welcome such changes.
>>
>
> That's an interesting idea. However, in this case, I think we need to
> pass the build options (from the parsed command-line arguments) along
> somehow. How should we set the build options when using the declarative
> 'computed-file' procedure? It seems like the most obvious way would be
> to pass the build options in as arguments to the 'computed-file'
> procedure, but is there a better way?
Which build options? There’s a direct correspondence between, say,
‘gexp->derivation’ and ‘computed-file’ and the arguments are essentially
the same. Unless I’m overlooking something (again!), the change I
suggest above is a mechanical change.
HTH,
Ludo’.
prev parent reply other threads:[~2016-10-19 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 6:21 Patches to implement system roll-back and switch-generation Chris Marusich
2016-10-04 10:01 ` Ludovic Courtès
2016-10-09 6:22 ` Chris Marusich
2016-10-11 21:05 ` Ludovic Courtès
2016-10-16 6:28 ` Chris Marusich
2016-10-19 21:07 ` Ludovic Courtès [this message]
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=87y41k2gkj.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@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.