From: Ricardo Wurmus <rekado@elephly.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: zimoun <zimon.toutoune@gmail.com>, gwl-devel@gnu.org
Subject: Re: [PATCH] workflow: Consider unspecified free inputs when checking cache.
Date: Wed, 26 Jun 2019 09:05:42 +0200 [thread overview]
Message-ID: <87ftnwsu61.fsf@elephly.net> (raw)
In-Reply-To: <87ef3hceuc.fsf@kyleam.com>
Hi Kyle,
> (5) the workflow unambiguously specifies how to generate each output.
> I don't want to have to document that "to generate THIS, you
> should run `guix workflow --input=THIS=THAT'". I want to make a
> blanket statement that "you can run `<workflow cmd> TARGET' to
> generate any desired output, which will do whatever is needed to
> make that happen". (I know this isn't currently possible with
> GWL.)
Spoken like a Snakemake user :)
The GWL has no fleshed out concept of targets, at least not in the way
that GNU Make presents them to the user. The GWL’s primary abstraction
is the process.
However, we should be able to tell the GWL to only run those processes
that are required to reach a certain output. This would require a
procedure that sections the graph of workflow processes.
--
Ricardo
prev parent reply other threads:[~2019-06-26 7:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 3:48 [PATCH] workflow: Consider unspecified free inputs when checking cache Kyle Meyer
2019-06-24 13:54 ` Ricardo Wurmus
2019-06-25 4:30 ` Kyle Meyer
2019-06-25 17:33 ` zimoun
2019-06-25 18:33 ` Ricardo Wurmus
2019-06-26 1:31 ` Kyle Meyer
2019-06-26 7:05 ` Ricardo Wurmus [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
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=87ftnwsu61.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=zimon.toutoune@gmail.com \
/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).