Re: Handling application private libs
On Sun, Sep 22, 2002 at 08:54:19PM +0900, Junichi Uekawa wrote:
> Devin Carraway <debian@devin.com> immo vero scripsit:
>
> > 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.
>
> What would be the point of restricting the shared libraries to within the
> software ?
Sometimes this happens because it makes sense to share the library within
the (to conserve resources), but either:
- It does not make sense for other programs to use the library (very
specific)
- The author is not willing to maintain a stable ABI or version the library
appropriately
--
- mdz
Reply to: