all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: 45312@debbugs.gnu.org
Subject: [bug#45312] [PATCH] ssh: Use 'guix repl' instead of 'guile'.
Date: Wed, 23 Dec 2020 16:06:47 +0100	[thread overview]
Message-ID: <87k0t8wohk.fsf@gnu.org> (raw)
In-Reply-To: <20201218105101.27869-1-ludo@gnu.org> ("Ludovic Courtès"'s message of "Fri, 18 Dec 2020 11:51:01 +0100")

Ludovic Courtès <ludo@gnu.org> skribis:

> This simplifies setup of build machines: no need to install Guile in
> addition to Guix, no need to set 'GUILE_LOAD_PATH' & co., leading to
> fewer failure modes.
>
> * guix/ssh.scm (remote-run): New procedure.
> (remote-daemon-channel): Use it instead of 'open-remote-pipe*'.
> (store-import-channel)[import]: Remove check for module availability.
> Add call to 'primitive-exit'.
> Use 'remote-run' instead of 'open-remote-pipe'.
> (store-export-channel)[export]: Remove check for module availability.
> Add calls to 'primitive-exit'.
> Use 'remote-run' instead of 'open-remote-pipe'.
> (handle-import/export-channel-error): Remove 'module-error' clause.
> (report-module-error): Remove.
> * guix/scripts/offload.scm (assert-node-has-guix): Replace call to
> 'report-module-error' by 'leave'.
> * doc/guix.texi (Daemon Offload Setup): Remove mention of Guile.
> ---
>  doc/guix.texi            |  2 +-
>  guix/scripts/offload.scm |  3 +-
>  guix/ssh.scm             | 91 +++++++++++++++++++++-------------------
>  3 files changed, 51 insertions(+), 45 deletions(-)

Pushed as 7624ebbae33cf49dded5e9032ed426781c9554f6!

Ludo’.




      reply	other threads:[~2020-12-23 15:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-18 10:51 [bug#45312] [PATCH] ssh: Use 'guix repl' instead of 'guile' Ludovic Courtès
2020-12-23 15:06 ` 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=87k0t8wohk.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=45312@debbugs.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.