Re: Handling application private libs
On Mon, Sep 23, 2002 at 11:49:50PM +0900, Junichi Uekawa wrote:
> Matt Zimmerman <mdz@debian.org> immo vero scripsit:
>
> > 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)
>
> But we all know that it is very often untrue :)
But this does not matter if the second point is true...
> > - The author is not willing to maintain a stable ABI or version the library
> > appropriately
>
> And we all know that in terms of Debian, they get to keep their
> ABI for 2 years, at least ... ;P
>
>
> If it is autoconfiscated source, making them not use shared
> libs is usually only "--enable-shared=no" away...
Why would you want to disable the shared library when it can provide great
benefits, such as when a number of frequently executed programs can share a
large portion of their codebase?
--
- mdz
Reply to: