[csw-maintainers] static libraries lib*.a in our packages

[Mike Watters]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter FELECAN wrote:
> I cannot recollect precisely if we already had this discussion. Phil and
> me, we had an exchange on this subject and I would like to have the
> opinion of the other fellow maintainers as our point of view are not
> totally convergent.
> 
> The questions are:
> 
> 1. Is a good practice for CSW packages to contain library archives of
>    the form lib*.a when we deliver dynamic libraries lib*.so ?
> 
> 2. What's the potential usage for such libraries?
> 
> 3. Which mechanism do you use for not building (e.g. ./configure
>    --disable-static) or to post-install (in the sense of after make install)
>    remove them.
> 
> Thank you in advance for your answers and comments.

I would say if we are compiling a library that offers both static and shared
we compile them both.  there are specific instances when a user or an admin
may need to compile a tool statically ( albeit very rare ).

If we are compiling an "application" that offers both static and dynamic.
I would say compile them both and offer the static in a devel package along
with the headers.

My Rational:

There are companies that use small boxes as member interface points,
particularly Credit Card Companies.  these are boxes that live all over the
world, some have dial-up modems attached to them for access, some have x.25
interfaces (no I am not kidding), and bandwidth is at a premium.
The static binary may be bigger then the dynamic one, but on the whole, the one
static binary will be smaller then the possibly multiple packages.


- --

Thanks,
Mike

"Any intelligent fool can make things bigger, more complex,
and more violent.  It takes a touch of genius -- and a lot of courage --
to move in the opposite direction."

* Albert Einstein 1879 - 1955
    US German-born Theoretical Physicist
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (SunOS)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknc5/cACgkQLrhmsXMSLxdIfwCfVFuQg9lhvkxL2dWT5do0ILJz
150An3kCntXhYuPpijBXv3NIK+UaYzAG
=sNat
-----END PGP SIGNATURE-----