Bug#146023: suggested patch against policy, documenting "libexec", or current custom on use of "lib" for binaries in lib* packages
Package: debian-policy
Severity: wishlist
I think this was discussed enough in -devel already, but
some good points about /libexec was given.
I've noticed that some known good practice is not documented in policy,
and I propose the following patch:
>diff -u policy.sgml{.orig,}
--- policy.sgml.orig Tue May 7 01:06:15 2002
+++ policy.sgml Tue May 7 01:11:23 2002
@@ -5598,6 +5598,15 @@
</p>
<p>
+ If your package has some run-time support programs that
+ are required by the shared library, or some unversioned plugin
+ .so files, that may be part of the shared library package.
+ However, to avoid filename clashes, the run-time support
+ binaries or plugins should reside under the directory
+ <tt>/usr/lib/<var>libraryname</var><var> soversion/</var></tt>
+ </p>
+
+ <p>
If you have several shared libraries built from the same
source tree you may lump them all together into a single
shared library package, provided that you change all of
--
dancer@debian.org : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: