[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg-shlibdeps and private libraries


Le mardi 13 novembre 2007 à 11:01 -0800, Steve Langasek a écrit :
> > 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

But when you keep private libraries without a stable ABI nor proper
soname versioning, you increase the chance that other packages start
using them without thinking. I'd say that the best solution is to put
the libraries in a separate package and ensure their versioning, but
it's more work and another cause of 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.

Given the number of specific binaries and libraries in this case, I hope
we will have some generic tools to make them support multiarch.

: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=

Reply to: