From: Ricardo Wurmus <rekado@elephly.net>
To: gwl-devel@gnu.org
Subject: name conflicts with “guix process”
Date: Sat, 19 Jan 2019 13:53:26 +0100 [thread overview]
Message-ID: <875zukg661.fsf@elephly.net> (raw)
Hi,
one of the interesting ideas that the GWL enables is that the people who
*use* processes don’t need to be the ones who created them. A user
could install a bunch of process definitions (by having them on
GUIX_WORKFLOW_PATH) and run them with “guix process” or combine them in
a custom workflow.
Unfortunately, this doesn’t scale so well, as processes provided by
different people may very well have the same names.
Does it make sense to expose processes at the user interface? Or should
processes really only ever be used in the context of workflows? A user
could still combine processes to a custom workflow, but the composition
would be done by writing a workflow definition and using the modules
that provide the processes.
This means that we could get rid of a top-level “guix process” and
subsume the remaining features under a single “guix workflow” command.
There could be a “guix workflow --list-processes” command that lists
processes, their description, and their module name.
What are your thoughts on this?
--
Ricardo
next reply other threads:[~2019-01-19 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 12:53 Ricardo Wurmus [this message]
2019-01-19 15:22 ` name conflicts with “guix process” zimoun
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=875zukg661.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
/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).