Re: 1.6.0 problems with libguilereadline-v-12 and fix

[Marius Vollmer]

address@hidden (Paul Jarc) writes:

> > Why is that better than always and system-wide prepending $(libdir) to
> > LD_LIBRARY_PATH?
> 
> It's less error-prone.  LD_LIBRARY_PATH can be gotten wrong after
> installation - by users.  Whereas if Guile looks in libdir
> automatically (as it could with a fixed libltdl), then as long as
> installation was done correctly, users can't shoot themselves in the
> foot that way.

But that might come back to hunt them later.  Guile will be able to
magically find libraries that can't otherwise be found.  I really do
strongly believe that when you install software into /usr/local but
the system can't find shared libraries in /usr/local/lib by default,
then the system is not correctly configured, not the package that has
been installed into /usr/local.  Same with any other prefix.

> > You do need a long PATH already, no?
> 
> No.  All commands are symlinked in /command, so that's the only
> directory in my global PATH.  But that's a wart, it's one more thing
> to have to maintain, and I don't want to have to create a similar one
> for libraries.

Everything thing else will be a bigger wart, in my opinion.  You might
not want to deal with it, but Guile is not the place to take care of
it, either.

-- 
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3  331E FAF8 226A D5D4 E405