Add a recommendation for the location for run-time support material,

Author: srivasta
Date: 2005/02/05 01:48:49
Add a recommendation for the location for run-time support material,
not meant to be invoked directly.
a) it shows a predilection for a directory named for the package,
but does not mandate it
b) Since this is a new requirement, it starts off as a
recommendation (after all, this was originally touted merely as
"best practice", not as something required for interoperability)
c) It also discusses arch independent modules, and adds similar
language for that.

git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-283

diff --git a/debian/changelog b/debian/changelog
index 2075a4476aaf5055b351cb6c6804e25c5e2e2d0a..c60c16fa15cbefd53ecb112d59e5aea12ac2472a 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -35,6 +35,9 @@ debian-policy (3.6.2.1) unstable; urgency=low
     informative footnote.                                    (Closes: #290270).
   * Bug fix: "debian-policy: virtual package request: mpd-client", thanks
     to Eric Wong                                             (Closes: #270020).
+  * Bug fix: "[ACCEPTED 2005/02/04]: "libexec", or use of "lib" for
+    binaries in lib* packages", thanks to Junichi Uekawa 
+                                                              (Closes: #146023). 
 
  --
 

diff --git a/policy.sgml b/policy.sgml
index b6502d6b9b560c0a6d8dd62dddffad5abb3c7261..2c596c297184a80a35ec29b9ff27cee7a1c76fd6 100644 (file)
--- a/policy.sgml
+++ b/policy.sgml
@@ -4395,6 +4395,22 @@ Replaces: mail-transport-agent
        <package><var>libraryname</var>-<var>soversion</var>-dev</package>
        instead.
       </p>
+
+        <p>                                                                 
+          If your package includes run-time support programs that            
+          do not need to be invoked manually by users, but are               
+          nevertheless required  for the package to function, then it        
+          is recommended that these programs are placed                      
+          (if they are binary) in a subdirectory of                          
+          <file>/usr/lib</file>, preferably under                            
+          <file>/usr/lib/</file><var>package-name</var>.                     
+          If the program is architecture independent, the                    
+          recommendation is for it to be placed in a subdirectory of         
+          <file>/usr/share</file> instead, preferably under                  
+          <file>/usr/share/</file><var>package-name</var>.                     
+        </p>                                                                 
+                                                                            
+
       <p>
        If you have several shared libraries built from the same
        source tree you may lump them all together into a single

diff --git a/upgrading-checklist.html b/upgrading-checklist.html
index 95e4e8bb824cb7dfd4ffba258a34f9aec0e1c0d7..9bd61ebbf9368386ccceb899efa9ca3e9e9f64d7 100644 (file)
--- a/upgrading-checklist.html
+++ b/upgrading-checklist.html
@@ -53,9 +53,11 @@ picking your way through this list.
 <h2>The checklist</h2>
 
 <pre>
-3.6.2.0                        2004
+3.6.2.0                        2005
      * Recommend doc-base, and not menu, for registering package documentation.
-     
+     * Run time support programs should live in subdirectories of
+       /usr/lib/ or /usrshare, and preferably the shared lib is named
+       the same as the package name (to avoid name collisions). [8.1]
 
 3.6.1.0                    Aug 2003
      + Prompting the user should be done using debconf. Non debconf