Re: dpkg-shlibdeps and private libraries
On Tue, Nov 06, 2007 at 08:51:05AM +0100, Andreas Tille wrote:
> At installation time the filles will be installed to a directory
> ARB_HOME=/usr/lib/arb
> were the binaries go to
> ${ARB_HOME}/bin
> The current packages install the dynamic libraries simply to /usr/lib
> which I want to fix now. They should go to
> ${ARB_HOME}/lib
FWIW, I don't agree that this is a fix. In one sense it makes /usr/lib
"cleaner" by moving private libs into a private directory; however:
- Because Debian uses ldconfig, the runtime cost of having additional
libraries in the search path for other apps is negligible
- By moving the libs out of the default search path, you introduce the
possibility that an unrelated library will have the same name in /usr/lib;
this is a potential source of user confusion, as well as
difficult-to-diagnose corner-case bugs
- When multiarch matures (or we have some other reason to move library
directories around...), your package will require specific handling to
update the library paths, rather than a simple change to libdir that will
be handled automatically by the ld.so search path.
So I think it's better to leave these libraries in /usr/lib instead of using
rpath.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
vorlon@debian.org http://www.debian.org/
Reply to: