I hereby second this proposal.
The original proposer did not supply any proposed textual changes to
policy, so I suggest the following as replacement text for the first
paragraph of 11.2:
--------------------------------------------------------------------------------
In general, libraries must be available in both shared and static forms.
In some cases, it is acceptable for a library to be available in static
form only; these cases include:
* libraries for languages whose shared library support is immature or
unstable;
* libraries whose interfaces are in flux or under development (commonly
the case when the library's major version number is zero, or where the
ABI breaks across patchlevels);
* libraries which are explicitly intended to be available only in static
form by their upstream author(s)
The shared version must be compiled with -fPIC, and the static version must
not be. In other words, each *.c file will need to be compiled twice.
--------------------------------------------------------------------------------
If the original submitter (Florian Weimer) objects to the above language,
please speak up.
Aside from providing the exception cases for shared libraries, I eliminated
the existing language which mandates what the shared and static library
packages "must" be named, because policy 11.3 covers this subject in
greater detail and could be construed to contradict the existing policy
11.2 in this respect. I made no other changes.
Richard, Wichert, would you guys care to second this proposal?
--
G. Branden Robinson |
Debian GNU/Linux | If ignorance is bliss,
branden@debian.org | is omniscience hell?
http://people.debian.org/~branden/ |
Attachment:
pgpyTrtnYhWNL.pgp
Description: PGP signature