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

Hi Liliana,

Well, I am in favor to go one foot then the other. :-)  Let start to
have a simple extension that we can improve by incremental changes,
then let add a section in the manual for having the reference
documentation, then let add a cookbook entry, etc.  Well, somehow the
perfect is the enemy of the good. :-)

It appears to me more motivational to document Guix extensions step by
step, i.e., people can contribute to the improvements, etc..  Instead
of going my way alone and then come back with a complete work.  For
what my opinion is worth.


On Fri, 7 Oct 2022 at 20:21, Liliana Marie Prikler
<liliana.prikler@gmail.com> wrote:

> 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.

The answer of this is provided by the following part of my previous message. :-)


> > 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---

The already included extension 'guix-modules' is usable using the
snippet above.  And we teach people via a blog post on hpc.guix.info.


> > --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---

> 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.

As shown by my snippet above, it does not work; at least on foreign distro.

Cheers,
simon




  reply	other threads:[~2022-10-07 18:50 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
2022-10-07 18:49           ` zimoun [this message]
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=CAJ3okZ1-kLa8Q_gEVmYzDiwVc13KTLA+oJxU1cbB9fUbRkm5SA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=58339@debbugs.gnu.org \
    --cc=liliana.prikler@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.