From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36162@debbugs.gnu.org
Subject: [bug#36162] [PATCH 0/4] Add 'remote-eval'
Date: Tue, 11 Jun 2019 15:26:40 +0200 [thread overview]
Message-ID: <87pnnk9rsf.fsf@elephly.net> (raw)
In-Reply-To: <20190610210853.5709-1-ludo@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> This patch series add ‘remote-eval’, which takes a gexp, remotely deploys
> everything the gexp refers to, and evaluates it (see
> <https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00127.html> for
> the initial discussion.) So you can have gexps like:
>
> #~(execl #$(file-append ffmpeg "/bin/ffmpeg") …)
>
> When you evaluate it, this specific ‘ffmpeg’ will be deployed over there.
> Another example is:
>
> (with-imported-modules (source-module-closure '((gnu services herd)))
> #~(begin
> (use-modules (gnu services herd))
> (map live-service-provision (current-services))))
> This gexp, when evaluated remotely, will use your very own (gnu services
> herd) module and the corresponding Guile (so if you’re on Guile 3 and the
> remote is still on Guile 2, that’s fine: Guile 3 will first be deployed
> there.)
>
> ‘remote-eval’ allows you to build locally and send the build results,
> or to send the derivations and build remotely.
This is great and just what I need for the install-berlin.scm script in
the “maintenance” repository where I need to deploy a particular version
of Guix to the target system before using that version of Guix to
reconfigure the remote system.
Thank you!
--
Ricardo
next prev parent reply other threads:[~2019-06-11 13:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 21:08 [bug#36162] [PATCH 0/4] Add 'remote-eval' Ludovic Courtès
2019-06-10 21:41 ` [bug#36162] [PATCH 1/4] gexp: Add 'lower-gexp' and express 'gexp->derivation' in terms of it Ludovic Courtès
2019-06-10 21:41 ` [bug#36162] [PATCH 2/4] Add (guix repl) Ludovic Courtès
2019-06-10 21:41 ` [bug#36162] [PATCH 3/4] inferior: Add 'read-repl-response' Ludovic Courtès
2019-06-10 21:41 ` [bug#36162] [PATCH 4/4] Add (guix remote) Ludovic Courtès
2019-06-11 13:26 ` Ricardo Wurmus [this message]
2019-06-11 17:35 ` [bug#36162] [PATCH 0/4] Add 'remote-eval' Jakob L. Kreuze
2019-06-12 13:45 ` Ludovic Courtès
2019-06-12 15:12 ` Jakob L. Kreuze
2019-06-13 11:09 ` Ludovic Courtès
2019-06-13 13:18 ` Jakob L. Kreuze
2019-06-13 16:17 ` Jakob L. Kreuze
2019-06-14 11:20 ` Ludovic Courtès
2019-06-30 13:24 ` Christopher Lemmer Webber
2019-07-04 16:22 ` Ludovic Courtès
[not found] <875zpgrjqf.fsf@sdf.lonestar.org>
[not found] ` <87h88x7pni.fsf@gnu.org>
[not found] ` <871s01l4c2.fsf@sdf.lonestar.org>
2019-06-11 0:35 ` Jakob L. Kreuze
2019-06-12 13:52 ` Ludovic Courtès
2019-06-12 15:43 ` Jakob L. Kreuze
2019-06-12 20: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=87pnnk9rsf.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=36162@debbugs.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).