From: Ricardo Wurmus <rekado@elephly.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: gwl-devel@gnu.org
Subject: Re: [Bug?] Cannot use Guix Workflow Language on Guix System
Date: Wed, 03 Jul 2019 16:53:06 +0200 [thread overview]
Message-ID: <87sgrntbjh.fsf@elephly.net> (raw)
In-Reply-To: <20190703132504.4vxrdbscwwz3vpnj@pelzflorian.localdomain>
Hi Florian,
thanks for your message!
> I hope this is the right mailing list.
It is!
> (the website appears to be down)
Oh, it crashed… I fixed the bug causing the crash and the site is up
again.
> How can I use the Guix Workflow Language on Guix System? I tried
> `guix package -i gwl` as described on
> <https://www.guixwl.org/getting-started>
The version of the gwl that’s currently available in Guix is pretty old
and I’ve been meaning to make a new release as soon as I get around to
fixing an annoying bug (in “load-workflow”).
> but the guix process and guix workflow commands do not become
> available.
Hmm. I’m only ever using it from a git checkout with “./pre-inst-env
guix workflow” and that works just fine. The behaviour you describe
sounds like a bug, though.
FWIW “guix process” no longer exists in the latest version, and
“GUIX_WORKFLOW_PATH” has been removed — workflows are now executed
directly from files and are no longer arranged in Guile modules.
The relationship to Guix as an extension is … difficult. I’m evaluating
a few changes for the future, such as whether it would make sense to use
“guix repl” instead of directly extending Guix.
> On Debian I had written a Guix workflow to deploy a not-yet-public
> Haunt website to a shared hosting provider and tried to use it on Guix
> now. (I hope that is a legitimate use case; I used gwl because I can
> specify package inputs.)
Interesting. While the primary audience is HPC users with scientific
workflows where parallel execution of processes on a cluster is
desirable, I guess building a website automatically with GWL processes
would work fine. Personally, I’d probably directly use a Guix build
script because this workflow does not seem to benefit much from parallel
execution.
--
Ricardo
next prev parent reply other threads:[~2019-07-03 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 13:25 [Bug?] Cannot use Guix Workflow Language on Guix System pelzflorian (Florian Pelz)
2019-07-03 14:53 ` Ricardo Wurmus [this message]
2019-07-03 21:23 ` pelzflorian (Florian Pelz)
2019-07-03 21:24 ` pelzflorian (Florian Pelz)
2019-07-03 15:00 ` zimoun
2019-07-03 15:36 ` Ricardo Wurmus
2019-07-03 15:53 ` zimoun
2019-07-03 18:49 ` Ricardo Wurmus
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=87sgrntbjh.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=gwl-devel@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).