unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: support for containers
Date: Tue, 29 Jan 2019 11:22:54 +0100	[thread overview]
Message-ID: <CAJ3okZ2wPOLJgR=d2J_1=SM7=F06pR1++nN4_BNdvsTWWr+3Sw@mail.gmail.com> (raw)
In-Reply-To: <87bm40qta0.fsf@elephly.net>

Hi Ricardo,

On Tue, 29 Jan 2019 at 00:08, Ricardo Wurmus <rekado@elephly.net> wrote:

> the GWL could already support execution in containers with this patch:

Nice !


> --8<---------------cut here---------------start------------->8---
> diff --git a/gwl/processes.scm b/gwl/processes.scm
> index b7251db..9ec5925 100644
> --- a/gwl/processes.scm
> +++ b/gwl/processes.scm
> @@ -19,13 +19,20 @@

[...]

> -(define (procedure->gexp process)
> +(define* (procedure->gexp process #:key (container? #t))
>    "Transform the procedure of PROCESS to a G-expression or return the
>  plain S-expression."

Why the default is #t ?


> The directories to be mounted in the container are derived from the
> declared inputs and outputs.  The only problem is that inputs are
> read-only in this implementation.  I like it this way, actually, but it
> means that the extended example workflow won’t work as it tries to
> delete its inputs.
>
> Should data inputs be declared as (mutable-file …) or (file …) instead
> of being plain strings?

Hum? I am not sure that it should a good design to declare inputs as mutable.


All the best,
simon

  parent reply	other threads:[~2019-01-29 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 23:03 support for containers Ricardo Wurmus
2019-01-29  9:38 ` Ricardo Wurmus
2019-01-29 10:39   ` zimoun
2019-01-29 11:46     ` Ricardo Wurmus
2019-01-29 14:29       ` zimoun
2019-01-29 17:19         ` Ricardo Wurmus
2019-01-29 21:52           ` zimoun
2019-01-29 23:16             ` Ricardo Wurmus
2019-01-30 10:17               ` zimoun
2019-01-30 12:46                 ` Ricardo Wurmus
2019-01-29 10:22 ` zimoun [this message]
2019-01-29 11:44   ` Ricardo Wurmus

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://www.guixwl.org/

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

  git send-email \
    --in-reply-to='CAJ3okZ2wPOLJgR=d2J_1=SM7=F06pR1++nN4_BNdvsTWWr+3Sw@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=gwl-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. 
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).