Bug#100346: [AMENDMENT 2001-07-30] permitting shared versions of libraries to not exist
retitle 100346 [AMENDMENT 2001-07-30] permitting shared versions of libraries to not exist
severity 100346 normal
thanks
This is a proposal to replace the first paragraph of Policy 11.2.
Originally proposed by Florian Weimer on Sun, 10 Jun 2001 00:50:14
+0200 in Message-Id: <E158rYc-0005S8-00@mercury.rus.uni-stuttgart.de>.
Seconded by Branden Robinson on Sat, 28 Jul 2001 17:55:10 -0500 in
Message-ID: <20010728175509.A28616@deadbeast.net>.
Seconded by Manoj Srivastava on Mon, 30 Jul 2001 21:36:57 -0500 in
Message-ID: <87wv4prfhy.fsf@glaurung.green-gryphon.com>.
Full text of amendement, including edits from Manoj Srivastava and
Richard Braakman follows.
I propose only a 1-week discussion period for this amendment, since
almost 2 weeks have passed since it was last discussed, and there were
no issues of contention at that time.
************************************************************************
In general, libraries must have a shared version in the library package
and a static version in the development package. The shared version
must be compiled with '-fPIC', and the static version must not be
(source files will thus typically need to be compiled twice).
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)
If a shared version of a library package is not desired and the reason
is not listed above, the maintainer should seek consensus for the
decision on the debian-devel mailing list. In any case, any library
that does not provide a shared version should discuss why in its
package's extended description. If a library is available only in
static form, then it must follow the conventions for a development
package.
************************************************************************
--
G. Branden Robinson | The key to being a Southern
Debian GNU/Linux | Baptist: It ain't a sin if you
branden@debian.org | don't get caught.
http://people.debian.org/~branden/ | -- Anthony Davidson
Reply to: