From: Julien Lepiller <julien@lepiller.eu>
To: "Gábor Boskovits" <boskovits@gmail.com>,
"Ricardo Wurmus" <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Extending Guix without using the Guile load path
Date: Wed, 19 Feb 2020 15:40:41 -0500 [thread overview]
Message-ID: <AD8530FE-B561-41F0-80C2-CE082D23FEE0@lepiller.eu> (raw)
In-Reply-To: <CAE4v=pioP5D2ZfyRJy25cz+KNEQ3CvxYcO-N+hKeBUHxj6E-Xg@mail.gmail.com>
Le 19 février 2020 14:46:55 GMT-05:00, "Gábor Boskovits" <boskovits@gmail.com> a écrit :
>This looks interesting.
>
>Ricardo Wurmus <rekado@elephly.net> ezt írta (időpont: 2020. febr. 19.,
>Sze
>16:37):
>
>> Hi Guix,
>>
>> I think it’s a bit difficult to install the Guix Workflow Language at
>> this point and I’d like to change that.
>>
>> Currently, new sub-commands for Guix are looked up by module name on
>the
>> Guile load path. When installing the “gwl” package, though, the
>Guile
>> load path is not automatically altered, so users need to set it up by
>> themselves. The load path is only altered automatically when users
>> install the “guile” package. This is not a good recommendation
>because
>> users may have Guile 2.2 in their profile, and not Guile 3.0 or
>whatever
>> version may be needed by the extension.
>>
>> I wonder if we can make this a little nicer by letting Guix look for
>> sub-command scripts in directories that are listed in an environment
>> variable, such as GUIX_EXTENSIONS_PATH. The “guix” package would set
>> this search path and packages wanting to provide a sub-command (such
>as
>> “guix workflow” or “guix home”) would arrange to have their scripts
>> placed in that sub-directory of their outputs.
>>
>
>I have encountered this with guix home, and one of my first setups was
>to
>adjust the path.
>
>
>> What do you think?
>>
>
>I believe this is a good idea. I also think there is an open bug
>already
>for the home thing.
I have a workaround in the bash-home-type, but of course it's not at all convenient. Fixing this would help a lot :)
>
>
>> --
>> Ricardo
>>
>
>Best regards,
>g_bor
>
>>
>>
next prev parent reply other threads:[~2020-02-19 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 15:36 Extending Guix without using the Guile load path Ricardo Wurmus
2020-02-19 19:46 ` Gábor Boskovits
2020-02-19 20:40 ` Julien Lepiller [this message]
2020-03-12 13:29 ` Ludovic Courtès
2020-03-17 18:32 ` Joshua Branson
2020-03-17 19:36 ` Julien Lepiller
2020-10-31 22:53 ` Ricardo Wurmus
2020-10-31 22:53 ` Ricardo Wurmus
2020-11-01 22:23 ` Ludovic Courtès
2020-12-06 1:14 ` Ricardo Wurmus
2020-12-08 11:03 ` Ludovic Courtès
2021-01-05 10:18 ` [PATCH] Discover extensions via GUIX_EXTENSIONS_PATH 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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AD8530FE-B561-41F0-80C2-CE082D23FEE0@lepiller.eu \
--to=julien@lepiller.eu \
--cc=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).