Andy Wingo writes:
>> + (native-search-paths
>> + (list (search-path-specification
>> + (variable "GUILE_LOAD_PATH")
>> + (files '("share/guile/site/2.2")))
>> + (search-path-specification
>> + (variable "GUILE_LOAD_COMPILED_PATH")
>> + (files '("lib/guile/2.0/ccache"
>> + "share/guile/site/2.2")))))))
>>
>> (define-public guile-for-guile-emacs
>> (package (inherit guile-next)
>
> This doesn't look right to me; why is GUILE_LOAD_COMPILED_PATH pointing
> into share? Probably need to update the pointer into lib to use 2.2,
> also.
I'm wondering... Currently when switching environments from guile to
guile-next and back, I found that I need to unset
GUILE_LOAD_COMPILED_PATH; otherwise it gets appended to and that breaks.
Why is the `2.0' and `2.2' part of the GUILE_LOAD_COMPILED_PATH? If
guile would always append that (or also look in the directory with
MAJOR.MINOR appended), i.e. something like
lib/guile/ccache # GUILE_LOAD_COMPILED_PATH
lib/guile/ccache/2.0 # guile-2.0 appends 2.0
lib/guile/ccache/2.2 # guile-2.2 appends 2.2
wouldn't that help a lot with picking up the right .go files when
running different versions of guile?
Greetings, Jan
--
Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.nl
