unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Olivier Dion via <gwl-devel@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>,
	"gwl-devel@gnu.org" <gwl-devel@gnu.org>
Subject: Re: guix: workflow: command not found
Date: Tue, 26 Apr 2022 13:59:00 -0400	[thread overview]
Message-ID: <87bkwnhgkb.fsf@laura> (raw)
In-Reply-To: <zFZoVIo66HMiwtLH3Kg-MunHJaPcxmownYwmpj-cxZzlSv2sPk1VUr6qOk-4g1wmY32_1zD12WN5Iuo7HHnNikrgn3xn83wE0Kgh85dpDww=@protonmail.com>

On Tue, 26 Apr 2022, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
> Hi,
>
> I'm following the tutorial in the website (https://www.guixwl.org/tutorial), but I get this message when trying to the workflow command:
>
> guix workflow --help
> guix: workflow: command not found
> Try `guix --help' for more information.
>
> Also, "guix --help" does not list it, but "guix package -I" says it is installed:
>
> gwl 0.4.0 out
> /gnu/store/sdl9p9y1kj8macwcz4mjid6m3xd15wzz-gwl-0.4.0
>
> What could this be? I'm using Guix system.

I have this `wf-env` script for my research' workflows:

--8<---------------cut here---------------start------------->8---
#!/bin/sh

# I assume that you have gwl installed in one of the following profiles.
export GUIX_EXTENSIONS_PATH=$HOME/.guix-home/profile/share/guix/extensions:$HOME/.guix-profile/share/guix/extensions

guix time-machine --channels=./.channels.scm -- $@
--8<---------------cut here---------------end--------------->8---

Don't mind the time-machine stuff if you don't need it.  Just replace
the last line with `guix $@` and then `./wf-env workflow run my-wf.w`.

Regards,
old

-- 
Olivier Dion
oldiob.dev


  reply	other threads:[~2022-04-26 17:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-26 16:17 guix: workflow: command not found Luis Felipe
2022-04-26 17:59 ` Olivier Dion via [this message]
2022-04-26 18:07 ` Ricardo Wurmus
2022-04-26 20:03   ` Luis Felipe
2022-04-29  9:11   ` 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=87bkwnhgkb.fsf@laura \
    --to=gwl-devel@gnu.org \
    --cc=luis.felipe.la@protonmail.com \
    --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).