[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gwl-devel] support for containers
From: |
zimoun |
Subject: |
Re: [gwl-devel] support for containers |
Date: |
Tue, 29 Jan 2019 11:22:54 +0100 |
Hi Ricardo,
On Tue, 29 Jan 2019 at 00:08, Ricardo Wurmus <address@hidden> 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
- [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/28
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/29
- Re: [gwl-devel] support for containers, zimoun, 2019/01/29
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/29
- Re: [gwl-devel] support for containers, zimoun, 2019/01/29
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/30
- Re: [gwl-devel] support for containers, zimoun, 2019/01/29
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/29
- Re: [gwl-devel] support for containers, zimoun, 2019/01/30
- Re: [gwl-devel] support for containers, Ricardo Wurmus, 2019/01/30
Re: [gwl-devel] support for containers,
zimoun <=