Re: Extending Guix without using the Guile load path

Hi, Ricardo Wurmus skribis: > Keeping the directory tree of the extension separate from the “guix > pull” profile would ensure that the core features of Guix keep working, > no matter how badly broken an extension might be. Yeah. > So I’m thinking that we should instead define GUIX_EXTENSIONS_

Re: Extending Guix without using the Guile load path

Ludovic Courtès writes: > What if an extension could instead be a package installed next to Guix > and its channels in ~/.config/guix/current, and we use > ‘package-path-entries’ as is done in (gnu packages) to augment > ‘%load-path’ and ‘%load-compiled-path’? I’m not sure if that would compli

Re: Extending Guix without using the Guile load path

Hi! Ricardo Wurmus skribis: > Ludovic Courtès writes: > >> Hello! >> >> Ricardo Wurmus skribis: >> >>> 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

Re: Extending Guix without using the Guile load path

Ludovic Courtès writes: > Hello! > > Ricardo Wurmus skribis: > >> 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

Re: Extending Guix without using the Guile load path

Ludovic Courtès writes: > Hello! > > Ricardo Wurmus skribis: > >> 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

Re: Extending Guix without using the Guile load path

Le 17 mars 2020 14:32:59 GMT-04:00, Joshua Branson a écrit : >Ludovic Courtès writes: > >> >> (Though eventually, I do think something like Guix Home should be >part >> of Guix itself. :-)) > >May I ask is Guix Home similar to systemd homed? Or do they have >slightly different objectives? Fro

Re: Extending Guix without using the Guile load path

Ludovic Courtès writes: > > (Though eventually, I do think something like Guix Home should be part > of Guix itself. :-)) May I ask is Guix Home similar to systemd homed? Or do they have slightly different objectives? -- Joshua Branson Sent from Emacs and Gnus

Re: Extending Guix without using the Guile load path

Hello! Ricardo Wurmus skribis: > 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 >

Re: Extending Guix without using the Guile load path

Le 19 février 2020 14:46:55 GMT-05:00, "Gábor Boskovits" a écrit : >This looks interesting. > >Ricardo Wurmus 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. >>

Re: Extending Guix without using the Guile load path

This looks interesting. Ricardo Wurmus 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 > Gui

Extending Guix without using the Guile load path

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 alt