Re: Plugin Package Paths

Hi Peter, Peter Polidoro writes: > Maxim Cournoyer writes: > >> These programs should be patched to honor e.g. FREECAD_PLUGINS_PATH >> or >> similar. Then a 'native-search-path' specification can be attached >> to >> the freecad packaged, and finding freecad plugins will happen in any >> profi

Re: [TIP] Using (@@ module-name binding-name) sometimes might result in "unbound variable"

> This proposal is for the Guile manual, right? You are right. I should have created this thread in the guile mailing list. I just did it: https://lists.gnu.org/archive/html/guile-user/2023-09/msg9.html

Re: Plugin Package Paths

Maxim Cournoyer writes: These programs should be patched to honor e.g. FREECAD_PLUGINS_PATH or similar. Then a 'native-search-path' specification can be attached to the freecad packaged, and finding freecad plugins will happen in any profile. The FREECAD_PLUGINS_PATH should be written wi

Re: Plugin Package Paths

Hi, Peter Polidoro writes: > What is the proper way to package plugins when a packaged program > searches for them in the executable path rather than the profile path? > > I would like to package plugins for two programs, kicad and freecad, > and they both search for plugins by first finding the

Plugin Package Paths

What is the proper way to package plugins when a packaged program searches for them in the executable path rather than the profile path? I would like to package plugins for two programs, kicad and freecad, and they both search for plugins by first finding the path of the executable. Freecad u

Re: [TIP] Using (@@ module-name binding-name) sometimes might result in "unbound variable"

Hi, Thanks for sharing. On Tue, 12 Sep 2023 at 08:24, Rodrigo Morales wrote: > I used @@ as stated in the Guile manual [1], but I kept getting the error > "unbound variable" (please see below). Indeed. --8<---cut here---start->8--- $ guix repl GNU Guile 3.