From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>,
Olivier Dion <olivier.dion@polymtl.ca>
Cc: gwl-devel@gnu.org
Subject: Re: GWL as a build-automation
Date: Thu, 18 Aug 2022 17:00:09 +0200 [thread overview]
Message-ID: <86edxdbnra.fsf@gmail.com> (raw)
In-Reply-To: <87wndu415p.fsf@elephly.net>
Hi,
I am late to the party. :-)
On Mon, 06 Jun 2022 at 10:50, Ricardo Wurmus <rekado@elephly.net> wrote:
> It is not entirely surprising to me that the GWL can express this,
> because it has really simple abstractions: that of a process and that of
> a workflow consisting of processes.
[...]
> Perhaps there is space for a different tool that takes lessons from the
> GWL and Scsh alike, with a focus on command composition and shell
> abstractions. Perhaps that tool already exists and is called Metabash:
>
> https://github.com/artyom-poptsov/metabash
From my understanding, metabash allows to remotely run processes, i.e.,
distribute the pipeline. Somehow, it could be see as an extension of
Scsh.
However, a pipeline is a linear sequence of processes. When a workflow
is a DAG of processes. Therefore, it would appear difficult to me to be
able to express a build-system using only pipelines.
Last, it appears to me expected that GWL could be considered as a
build-system. A scientific workflow system [1] (as GWL) is just a
specialized implementation to deal with a graph of dependencies.
Software folks speak about the venerable Make as build automation
workflow, while bioinfo folks speak about a specific Python
implementation SnakeMake as data analysis workflow. Just the same
concepts but viewed by different communities. :-)
If I might, an interesting analysis of different strategies for dealing
with the graph of dependencies is done in the paper «Build systems à la
carte» [2]. It presents the various abstractions using Haskell
notations.
1: <https://en.wikipedia.org/wiki/Scientific_workflow_system>
2: <https://doi.org/10.1017/S0956796820000088>
Cheers,
simon
prev parent reply other threads:[~2022-08-18 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 22:21 GWL as a build-automation Olivier Dion via
2022-06-06 8:50 ` Ricardo Wurmus
2022-08-18 15:00 ` zimoun [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=86edxdbnra.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=olivier.dion@polymtl.ca \
--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.
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.