unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: stuebinm <stuebinm@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: guix workflow not found?
Date: Wed, 28 Apr 2021 23:06:10 +0200	[thread overview]
Message-ID: <87zgxim859.fsf@elephly.net> (raw)
In-Reply-To: <dede0c98-a09f-2ca2-a2cc-d4f0b9c9735f@disroot.org>


Hi stuebinm,

> (I hope this is the right place for this question)

I’m not sure! :)

This list is fine, but we also have a dedicated GWL list: 
https://lists.gnu.org/archive/html/gwl-devel/

> I'm on a newly installed Guix machine, and have done the 
> following:
>
>   guix pull
>   guix install gwl
>   guix workflow
>
> The output of the last is:
>
>   guix: workflow: command not found
>   Try `guix --help' for more information
>
> As far as I can see from the gwl installation instructions [1], 
> this
> should work out of the box. However, from inside guix repl I 
> also
> cannot load the (guix scripts workflow) module, so I assume that
> perhaps the GUIX_EXTENSIONS_PATH variable is set incorrectly, 
> even if
> it says it shouldn't be necessary to set it manually when on a 
> guix
> system (I don't really know what to set it to, however ...).

I’m sorry about this!  The documentation really is not clear 
enough here.  Annoyingly, you currently do need to set 
GUIX_EXTENSIONS_PATH manually.  The reason for that is that Guix 
doesn’t yet do this automatically when using “guix pull”.

There is also a reason why the documentation is so vague: we 
hadn’t really come to consensus about the exact behavior of 
GUIX_EXTENSIONS_PATH.  I intended to update the documentation once 
we had this figured out.

For now, I suggest you set it like this:

    export 
    GUIX_EXTENSIONS_PATH=$GUIX_PROFILE/share/guix/extensions/

where GUIX_PROFILE is the name of the profile directory where you 
installed the “gwl” package (in your case that’s likely just 
“$HOME/.guix-profile”).

~~~

I should also note that there are a couple of known bugs in the 
GWL at this point, and I’m working on adding a DRMAA backend to 
submit workflow jobs to an HPC cluster.  There is no date for a 
new release yet, but I guess that in a few more weeks we will have 
accumulated enough fixes and features to announce a new release.

If you have a particular use-case in mind, I’d be very happy if 
you could tell us about it on gwl-devel, so that we can make sure 
the GWL grows in a direction that is beneficial for you.

-- 
Ricardo


      reply	other threads:[~2021-04-28 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 18:01 guix workflow not found? stuebinm
2021-04-28 21:06 ` 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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zgxim859.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=stuebinm@disroot.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).