From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([209.51.188.92]:46785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hXoqv-0002Rm-2A for gwl-devel@gnu.org; Mon, 03 Jun 2019 11:26:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hXohG-0006Zt-5r for gwl-devel@gnu.org; Mon, 03 Jun 2019 11:16:27 -0400 Received: from mail-qk1-x72f.google.com ([2607:f8b0:4864:20::72f]:40222) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hXohG-0006XC-1I for gwl-devel@gnu.org; Mon, 03 Jun 2019 11:16:26 -0400 Received: by mail-qk1-x72f.google.com with SMTP id c70so632182qkg.7 for ; Mon, 03 Jun 2019 08:16:25 -0700 (PDT) MIME-Version: 1.0 References: <87a7f5l6e1.fsf@mdc-berlin.de> In-Reply-To: <87a7f5l6e1.fsf@mdc-berlin.de> From: zimoun Date: Mon, 3 Jun 2019 17:16:13 +0200 Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: Next steps for the GWL List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gwl-devel-bounces+kyle=kyleam.com@gnu.org Sender: "gwl-devel" To: Ricardo Wurmus Cc: gwl-devel@gnu.org Hi Ricardo, On Wed, 29 May 2019 at 16:41, Ricardo Wurmus wrote: > > I=E2=80=99m going to use the GWL in the next few days to rewrite the PiGx= RNAseq > pipeline from Snakemake. This will likely show me what features are > still missing from the GWL and what implemented features are awkward to > use. Awesome! > * tighter integration with Guix features, e.g. to export a container > image per process via =E2=80=9Cguix pack=E2=80=9D or to pack up the who= le workflow as > a relocatable executable. Yes! Awesome. Relocatable tarballs. Docker images. Singularity one. And maybe generate one pack (docker) per process and something to glue together, e.g., http://www.genouest.org/godocker/ > * explore the use of inferiors =E2=80=94 the GWL should be usable with an= y > version of Guix that may be installed, not just the version that was > used at compilation time. Can we use =E2=80=9Cguix repl=E2=80=9D and i= nferiors, > perhaps? For reproducibility, a Guix commit should be provided and a `guix pull` (inferiors) should be used. For example, the output of `guix describe -f channels` should be used, either with an option, either directly in the Scheme/Wisp workflow file with a new keyword. > > * add support for executing processes in isolated environments > (containers) =E2=80=94 this requires a better understanding of process = inputs. Maybe this is the same story than the GoDocker above. Talking about ideas: - what about the Content Adressable Store? - what about a bridge with CWL? Thank you to revive the list. :-) All the best, simon