[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Extending Guix without using the Guile load path

From: Julien Lepiller
Subject: Re: Extending Guix without using the Guile load path
Date: Wed, 19 Feb 2020 15:40:41 -0500
User-agent: K-9 Mail for Android

Le 19 février 2020 14:46:55 GMT-05:00, "Gábor Boskovits" <address@hidden> a 
écrit :
>This looks interesting.
>Ricardo Wurmus <address@hidden> ezt írta (időpont: 2020. febr. 19.,
>> 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
>> Guile load path.  When installing the “gwl” package, though, the
>> 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
>> users may have Guile 2.2 in their profile, and not Guile 3.0 or
>> 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
>> “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
>adjust the path.
>> What do you think?
>I believe this is a good idea. I also think there is an open bug
>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,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]