all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>, 58339@debbugs.gnu.org
Subject: [bug#58339] ’guix shell’ not working with GUIX_EXTENSIONS_PATH
Date: Fri, 07 Oct 2022 20:21:36 +0200	[thread overview]
Message-ID: <b41131281ab6cff3cb2121c81916c586f4523e3c.camel@gmail.com> (raw)
In-Reply-To: <871qrkujrh.fsf@gmail.com>

Am Freitag, dem 07.10.2022 um 10:21 +0200 schrieb zimoun:
> Hi Liliana,
> 
> Thanks for your feedback.
> 
> On jeu., 06 oct. 2022 at 21:58, Liliana Marie Prikler
> <liliana.prikler@gmail.com> wrote:
> 
> About this:
> 
> > 2. Testing the extension via `guix shell'
> 
> We need to open another issue because it is not related to the
> current patch (proposal for a simple example of an extensions); this
> point #2 is an issue about all the extensions.
But that's the point.  Simply adding an extension – whether an example
or an actually useful one – doesn't teach users how to use them.  It's
missing this very information among other things.

> For instance, let consider guix-modules [1].  It reads,
> 
> --8<---------------cut here---------------start------------->8---
> $ guix install guix-modules
> $ export GUIX_EXTENSIONS_PATH="$HOME/.guix-
> profile/share/guix/extensions"
> --8<---------------cut here---------------end--------------->8---
> 
> and if instead, one uses a shell, it fails:
> 
> --8<---------------cut here---------------start------------->8---
> $ guix shell guix-modules -- guix module -h
> guix: module: command not found
> Try `guix --help' for more information.
> 
> $ guix shell guix-modules
> [env]$ guix module -h
> guix: module: command not found
> Try `guix --help' for more information.
> --8<---------------cut here---------------end--------------->8---
> 
> Note that the variable GUIX_EXTENSIONS_PATH is listed in etc/profile,
> 
> --8<---------------cut here---------------start------------->8---
> [env]$ cat $GUIX_ENVIRONMENT/etc/profile
> # Source this file to define all the relevant environment variables
> in Bash
> # for this profile.  You may want to define the 'GUIX_PROFILE'
> environment
> # variable to point to the "visible" name of the profile, like this:
> #
> #  GUIX_PROFILE=/path/to/profile ; \
> #  source /path/to/profile/etc/profile
> #
> # When GUIX_PROFILE is undefined, the various environment variables
> refer
> # to this specific profile generation.
> 
> export GUIX_EXTENSIONS_PATH="${GUIX_PROFILE:-
> /gnu/store/qhfy9wwzg98a0j3i88qaxdmy19rvp0s8-
> profile}/share/guix/extensions${GUIX_EXTENSIONS_PATH:+:}$GUIX_EXTENSI
> ONS_PATH"
> --8<---------------cut here---------------end--------------->8---
> 
> Well, another issue with extensions. :-)
In case you really didn't know how to use extensions with guix shell,
it's guix shell guix your-extension -- guix blah, assuming your
extension works with a slightly older guix.

Cheers




  reply	other threads:[~2022-10-07 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 16:36 [bug#58339] [PATCH 0/2] Add simple Guix extensions as example zimoun
2022-10-06 16:39 ` [bug#58339] [PATCH 1/2] gnu: Add guix-hello zimoun
2022-10-06 16:39   ` [bug#58339] [PATCH 2/2] gnu: Add guix-example zimoun
2022-10-06 19:58     ` Liliana Marie Prikler
2022-10-07  8:21       ` [bug#58339] ’guix shell’ not working with GUIX_EXTENSIONS_PATH zimoun
2022-10-07 18:21         ` Liliana Marie Prikler [this message]
2022-10-07 18:49           ` zimoun
2022-10-07 19:28             ` Liliana Marie Prikler
2022-10-08  8:35               ` zimoun
2022-10-08  9:43                 ` Liliana Marie Prikler

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

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

  git send-email \
    --in-reply-to=b41131281ab6cff3cb2121c81916c586f4523e3c.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=58339@debbugs.gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.