On Jan 06, Nathanael Nerode <email address hidden> wrote:
> Good point. Let's amend policy to require that a _pic.a library be provi=
ded
> for any static-only library; it seems to be an unreasonable omission. I=
=20
> wouldn't consider a library package which can't be used by any shared lib=
rary=20
> to be releasable. Would anyone else?
It's a bit more complex than this, you can find a summary in http://blog.bofh.it/id_101 .
In this specific case, the solutions should be (in order of priority):
- remove freecdb from the archive, since there are better replacements
(providing a shared library is enough to make them better, at least)
- make freecdb provide a shared library (which should be easy, and the
opinion of DJB is not really intersting not relevant for our purposes)
- make freecdb provide a PIC static library
OTOH, the last two points are almost a pointless exercise if there is no
actual shared library which needs to be linked against freecdb.
--=20
ciao,
Marco
--jRHKVT23PllUwdXP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
Message-ID: <email address hidden>
Date: Fri, 6 Jan 2006 12:28:27 +0100
From: <email address hidden> (Marco d'Itri)
Cc: <email address hidden>, <email address hidden>
Subject: Re: Policy should require _pic libraries for static-only libraries
--jRHKVT23PllUwdXP Disposition: inline Transfer- Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Content-
Content-
On Jan 06, Nathanael Nerode <email address hidden> wrote:
> Good point. Let's amend policy to require that a _pic.a library be provi= blog.bofh. it/id_101 .
ded
> for any static-only library; it seems to be an unreasonable omission. I=
=20
> wouldn't consider a library package which can't be used by any shared lib=
rary=20
> to be releasable. Would anyone else?
It's a bit more complex than this, you can find a summary in
http://
In this specific case, the solutions should be (in order of priority):
- remove freecdb from the archive, since there are better replacements
(providing a shared library is enough to make them better, at least)
- make freecdb provide a shared library (which should be easy, and the
opinion of DJB is not really intersting not relevant for our purposes)
- make freecdb provide a PIC static library
OTOH, the last two points are almost a pointless exercise if there is no
actual shared library which needs to be linked against freecdb.
--=20
ciao,
Marco
--jRHKVT23PllUwdXP pgp-signature; name="signature .asc" Description: Digital signature Disposition: inline
Content-Type: application/
Content-
Content-
-----BEGIN PGP SIGNATURE-----
w2OHuP7ERAohvAJ 0VaTWlyDSNm+ hOR1E0pUUibP4BO QCePfVP nTVSTrH8=
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDvlRbFGf
GH49Zrma6ik180p
=vNwI
-----END PGP SIGNATURE-----
--jRHKVT23PllUw dXP--