From: Manoj Srivastava Date: Thu, 16 Jun 2005 05:45:17 +0000 (+0000) Subject: Clatrified section 8.1 to further demonstrate that section 8.1 is not X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=30a8dd895cb156a9a0e9080c78a72a3a6b511e21;p=debian%2Fdebian-policy.git Clatrified section 8.1 to further demonstrate that section 8.1 is not Author: srivasta Date: 2005/02/04 07:01:51 Clatrified section 8.1 to further demonstrate that section 8.1 is not a must directive, since some people seem to be confused about this. git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-278 --- diff --git a/policy.sgml b/policy.sgml index dd8275d..b238a14 100644 --- a/policy.sgml +++ b/policy.sgml @@ -4350,10 +4350,21 @@ Replaces: mail-transport-agent Run-time shared libraries

- The run-time shared library needs to be placed in a package called - librarynamesoversion, where - soversion is the version number in the - soname of the shared library + The run-time shared library needs to be placed in a package + whose name changes whenever the shared object version + changes. +

+ Since it is common place to install several versions of a + package that just provides shared libraries, it is a + good idea that that the library package should not + contain any extraneous non-versioned files, unless they + happen to be in versioned directories.

+ + The most common mechanism is to place it in a package + called + librarynamesoversion, + where soversion is the version number + in the soname of the shared library The soname is the shared object name: it's the thing that has to match exactly between building an executable and running it for the dynamic linker to be able run the @@ -4368,7 +4379,6 @@ Replaces: mail-transport-agent libraryname-soversion-dev instead.

-

If you have several shared libraries built from the same source tree you may lump them all together into a single