[Gllug] libs, but where?

tet at accucard.com tet at accucard.com
Fri Jul 26 03:02:03 UTC 2002

>I cannot see how you can *possibly* say that an option that forbids
>moving shared libraries around without relinking all binaries linked
>against them is preferable to one that allows moving of shared libraries
>at any time with no more difficulty than changing one path in one file
>and running /sbin/ldconfig.

The main problem with your argument is that it assumes you a) have
root access when installing software, and b) that the software will
only be used locally. Most of my software is installed in a shared NFS
environment, where it's certainly not feasible to modify each client
to look for libraries in the correct place. Sure, I *could* manully go
through and add a wrapper for every binary that sets LD_LIBRARY_PATH,
but using DT_R{,UN}PATH seems to me a much cleaner solution. I guess
my main problem with ld.so.conf is that it seems designed with a
single standalong machine mentality, which is the complete opposite of
what I primarily use Unix for (i.e., environments where I typically
install stuff for use by many people on many machines).

But then I guess neither of us represent the typical end user


Gllug mailing list  -  Gllug at linux.co.uk

More information about the GLLUG mailing list