I'm working on a package containing several executables, whose common functionality lives in a few shared libraries. They're linked in the usual way at compile time. Policy says they should live in /usr/lib/packagename/, but I need to make them available for the runtime linker.
I know of three ways to deal with this one -- add a new path to ld.so.conf (yuck), link with -rpath, or wrap the apps in a script which alters $LD_LIBRARY_PATH. None of these are thrilling; I gather that rpath is verboten, but haven't found any mention of it in the policy manual. The wrapper script approach seems the least problematic, but since the libs are in the package and the script would hardcode the path it doesn't seem inherently any better than -rpath. Suggestions? -- Devin \ aqua(at)devin.com, 1024D/E9ABFCD2; http://www.devin.com Carraway \ IRC: Requiem GCS/CC/L s-:--- !a !tv C++++$ ULB+++$ O+@ P L+++
msg07237/pgp00000.pgp
Description: PGP signature
