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

Re: Handling application private libs



On Sun, Sep 22, 2002 at 01:40:12PM -0600, Bob Proulx wrote:
> If you can avoid those shared libraries it would be best.  Libraries
> should be either shared in /usr/lib or not shared at all.  The halfway
> between place is not a mature methodology at this time and contains
> many problems.

Ignoring the irksome ld.so issues for a moment, upstram for this package
is doing exactly the right thing by putting common functionality out in
shared libs, even if the only executables sharing them are the ones in
the package itself.  There are 11 executables in this package, of about
30k each, plus 3 libs of about 75k each; each executable links against
two of the libs.  Linking the private libs statically would roughly
triple the size of the package.

There are plenty of packages using private subdirs of /usr/lib/ to store
shared libraries, though most seem to access them directly dlopen().



-- 
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+++

Attachment: pgpFy62ZfE03D.pgp
Description: PGP signature


Reply to: