On Thu, 2006-09-21 at 20:09 +0200, Roger Oberholtzer wrote:
export LD_LIBRARY_PATH=/path/to/your/library
and then executes the application that needs the special lib
This seems like a much nicer solution than to add extra directories to ld.so.conf for one particular app (and it beats the living daylights out
I cannot realistically wrap the applications in the offending package. Unless it is in some complicated and doomed to fail method, like an update from the packager that wipes out the modifications.
This I didn't understand at all. You are compiling the applications, aren't you? So we're not talking about modifying prepackaged software. So why not, as the final stage, make the name of the executable "name-bin" and make "name" be a script that exports the ld library path variable and then executes name-bin. This is not particularly complex, and it's far better than putting obscure specialty libraries in ld.so.conf, and it's far far better than hard coding It is, in fact, the method already used by many applications, such as mozilla and open office. Are they doomed to fail?