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

[Mike Watters]

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

Ben Walton wrote:
> Excerpts from Philip Brown's message of Wed Apr 08 14:01:50 -0400 2009:
>> Occasionally, there may be benefits to making a static library for some
>> software available for optional use. However, when and if the maintainer
>> decides there is a benefit to providing a static lib, it is best to do so
>> in a "devel" subpackage (unless the library is relatively small).
>>
>> Other folks, please add your thoughts to this :-)
> 
> This lines up with the Debian policy and sounds quite reasonable to
> me.  You shouldn't need the .a file unless you're building something
> against it anyway, so the dev package is a good spot for it.
> 
> To save others the google, here is the debian policy link:
> http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-static
> 
> -Ben
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> maintainers mailing list
> maintainers at lists.opencsw.org
> https://lists.opencsw.org/mailman/listinfo/maintainers

Fedora/Red Hat policy follows this convention as well.

and the following line quotes directly and I think it is the best rational.

"A good rule of thumb is if the file is used for development and not needed for
the base package to run properly, it should go in -devel."
http://fedoraproject.org/wiki/Packaging:Guidelines
- --

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

iEYEARECAAYFAknc6noACgkQLrhmsXMSLxefPQCfRoH8YnaYTjy3ZSmgkDecW+lW
iwkAoOTkvFhT6YQ04ZbhcFuSvvqeWL3q
=TvKO
-----END PGP SIGNATURE-----