From: Ricardo Wurmus <rekado@elephly.net>
To: Olivier Dion <olivier.dion@polymtl.ca>
Cc: gwl-devel@gnu.org
Subject: Re: Auto-create processe's output-path?
Date: Mon, 06 Jun 2022 12:26:49 +0200 [thread overview]
Message-ID: <87o7z63wzk.fsf@elephly.net> (raw)
In-Reply-To: <87mteta7pv.fsf@laura>
Olivier Dion <olivier.dion@polymtl.ca> writes:
> I have a pipeline of processes. These are all templated and I generate
> hundreds of these pipelines with different parameters. Everything is
> auto-connected with inputs/outputs matching. What is important to me is
> that all inputs/outputs of a pipeline are separated in different
> directories.
>
> Setting a working directory that is parameterizable for the processes
> would do this cleanly and I believe would also work in a containerized
> environment.
This sounds like a good idea. Better than “output-path”, which is hard
to understand, conceptually collides with “outputs”, and is used as a
prefix. Specifying a working directory sounds like an improvement.
Would you like to add a patch to that effect?
--
Ricardo
next prev parent reply other threads:[~2022-06-06 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 16:33 Auto-create processe's output-path? Olivier Dion via
2022-06-03 18:43 ` Ricardo Wurmus
2022-06-03 19:05 ` Olivier Dion via
2022-06-06 10:26 ` Ricardo Wurmus [this message]
2022-06-06 13:26 ` Olivier Dion via
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=87o7z63wzk.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=olivier.dion@polymtl.ca \
/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).