From 8714ea1b0fedf8009b6d7588988a97407daa48fe Mon Sep 17 00:00:00 2001
From: Manoj Srivastava
must not require a package outside of "main" for
compilation or execution (thus, the package must not
- declare a "Depends", "Recommends", or "Build-Depends"
- relationship on a non-main package),
+ declare a "Depends", "Recommends", or
+ "Build-Depends" relationship on a non-main package),
- Every package should have exactly one maintainer at a
- time. This person is responsible that the license of the
- package's software complies with the policy of the
- distribution this package is included in.
+ Every package must have a maintainer (the maintainer may
+ be one person or a group of people reachable from a common
+ email address, such as a mailing list). The maintainer is
+ responsible for ensuring that the package is placed in
+ the appropriate distribution
+
The maintainer must be specified in the
Maintainer control field with the correct name
@@ -1151,11 +1152,6 @@
making a new changelog entry rather than "rewriting history"
by editing old changelog entries)
- A copy of the file which will be installed in
- /usr/share/doc/package/copyright should be
- in debian/copyright.
In non-experimental packages you must only use a format for
debian/changelog which is supported by the most
@@ -2801,8 +2797,8 @@
This is done using the Depends, Recommends,
- Suggests, Conflicts, Provides and
- Replaces control file fields.
+ Suggests, Enhances, Conflicts,
+ Provides and Replaces control file fields.
@@ -2905,13 +2901,14 @@
- These four fields are used to declare a dependency by one
- package on another. They appear in the depending package's
- control file.
+ These five fields are used to declare a dependency
+ relationship by one package on another. They appear in the
+ depending package's control file.
@@ -2975,7 +2972,16 @@
perhaps enhance its usefulness, but that installing
this one without them is perfectly reasonable.
+ This field is similar to Suggests but works in the
+ opposite direction. It is used to declare that a
+ package can enhance the functionality of another
+ package.
+
User `nobody.'
User `nobody.' The corresponding gid refers + to the group `nogroup.'
+ Often there are some values in the `init.d' + scripts that a system administrator will frequently want + to change. While the scripts are frequently conffiles, + modifying them requires that the administrator merge in + their changes each time the package is upgraded and the + conffile changes. To ease the burden on the system + administrator, such configurable values should not be + placed directly in the script. Instead, they should be + placed in a file in `/etc/default', which + typically will have the same base name as the + `init.d' script. This extra file can be sourced + by the script when the script runs. It must contain only + variable settings and comments. +
+ ++ To ensure that vital configurable values are always + available, the `init.d' script should set default + values for each of the shell variables it uses before + sourcing the /etc/default/ file. Also, since the + `/etc/default/' file is often a conffile, the + `init.d' script must behave sensibly without + failing if it is deleted. +
+
+ Complementing the above init script is a file + '/etc/default/bind', which contains configurable + parameters used by the script. +
+
+
Another example on which to base your /etc/init.d scripts is in /etc/init.d/skeleton.
@@ -5063,7 +5124,7 @@
If a package needs any special device files that are not
included in the base system, it must call
-
@@ -5225,9 +5286,10 @@
- Packages that are not tagged as conflicting with
- each other must not specify the same file as
- conffile.
The maintainer scripts must not alter the conffile of @@ -5604,10 +5666,18 @@ /usr/bin/sensible-editor does.
- Since the Debian base system already provides an editor and - a pager program, it is not required for a package to depend on + It is not required for a package to depend on `editor' and `pager', nor is it required for a package to - provide such virtual packages.
+ provide such virtual packages. ++ The Debian base system already provides an editor and + a pager program, +
++ Files in /usr/share/doc should not be referenced by + any program, and the system administrator should be able to + delete them without causing any programs to break. Any files + that are referenced by programs but are also useful as + standalone documentation should be installed under + /usr/share/<package$gt;/ and symlinked in + /usr/share/doc/<package$gt;/. +
++ A copy of the file which will be installed in + /usr/share/doc/package/copyright should be + in debian/copyright.
+/usr/share/doc/<package-name> may be a symbolic link to a @@ -6387,7 +6474,7 @@ relationship on the second. These rules are important because copyrights must be extractable by mechanical means.
- +Packages distributed under the UCB BSD license, the Artistic license, the GNU GPL, and the GNU LGPL should refer to the diff --git a/upgrading-checklist.html b/upgrading-checklist.html index 8784dbe..91a344b 100644 --- a/upgrading-checklist.html +++ b/upgrading-checklist.html @@ -6,10 +6,10 @@ Author : Manoj Srivastava ( srivasta@tiamat.datasync.com ) Created On : Thu Oct 29 20:54:48 1998 Created On Node : tiamat.datasync.com - Last Modified By : Julian Gilbey - Last Modified On : Mon Jun 19 20:06:50 2000 - Last Machine Used: polya.maths.qmw.ac.uk - Update Count : 11 + Last Modified By : Manoj Srivastava + Last Modified On : Thu Jan 18 01:32:14 2001 + Last Machine Used: glaurung.green-gryphon.com + Update Count : 14 Status : Unknown, Use with caution! HISTORY : Description : @@ -44,10 +44,24 @@ Manual.
+3.2.1.1 Jan 01 + + Policy Manual: + - If your package has a daemon startup script in /etc/init.d/, + and that script has parameters a system administrator may need, + you need to modify the script to read values from a conffile + placed in /etc/default/ directory. This conffile maybe sourced + by the init.d script to determine the sonfigurable values (and + the conffile may contain only variable settings and comments). + - Files in /usr/share/doc may not be referenced by any + program. If such files are needed, they must be placed in + /usr/share/package-name/, and symbolic links created as required + in /usr/share/doc/package-name/ + 3.2.1.0 Aug 00 Policy Manual: - - A package of priority standard or hihger may provide two + - A package of priority standard or higher may provide two binaries, one compiled with support for the X Window System, and the other without. - -- 2.39.5