Sjoerd van Leent Privé <svanle...@gmail.com> writes:
> Just a quick note. Now with GUILE_SYSTEM_EXTENSIONS_PATH, this could
> be very practical when developing a module. However, if a module is
> already present AND is inside SCM_LIB_DIR or SCM_EXTENSIONS_DIR, it
> would never override that situation. I believe there should be a way
> to be able to override the normal behavior.
If GUILE_SYSTEM_EXTENSIONS_PATH is set, then neither SCM_LIB_DIR nor
SCM_EXTENSIONS_DIR are added to the search path. This is currently the
case, and my patch would not change that. There is one complication
though: SCM_LIB_DIR is normally $prefix/lib, which is usually in the
default system library search path.
However, it is still possible to override the normal behavior by
manually modifying LD_LIBRARY_PATH. Is there any reason why that's a
suboptimal solution for use when developing a module?
Having said this, I'm not convinced that my patch does the right thing.
I'm still trying to understand the needed requirements. I'll talk more
about this is my response to Ludovic.
Thanks for the feedback!
Regards,
Mark
