X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=3fcae7589b112d313dd0576d4dcdb080b8a63c1a;hb=81047fb3cf766bf985008a0754d0dd65cd82dd06;hp=f512315708535d5dc0691533da2f1ef7a48b8280;hpb=b6ec3caac4fc2ea5938a069b60558e140766f6c5;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index f512315..3fcae75 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -279,6 +279,14 @@
.
+
+
@@ -489,9 +497,9 @@
-
must not require or recommend 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),
+ package must not declare a "Pre-Depends", "Depends",
+ "Recommends", "Build-Depends", or "Build-Depends-Indep"
+ relationship on a non-main package),
-
must not be so buggy that we refuse to support them,
@@ -2696,7 +2704,7 @@ Package: libc6
This file consists of a single paragraph, possibly surrounded by
a PGP signature. The fields of that paragraph are listed below.
- Their syntax is described above, in [.
+ Their syntax is described above, in ][.
]
- Format (mandatory)
@@ -4628,7 +4636,7 @@ Depends: libc6 (>= 2.2.1), exim | mail-transport-agent
Relationships may be restricted to a certain set of
architectures. This is indicated in brackets after each
individual package name and the optional version specification.
- The brackets enclose a list of Debian architecture names
+ The brackets enclose a non-empty list of Debian architecture names
in the format described in [,
separated by whitespace. Exclamation marks may be prepended to
each of the names. (It is not permitted for some names to be
@@ -6246,33 +6254,33 @@ install -m644 debian/shlibs.package debian/package/DEBIAN/
symlinked there, is relaxed to a recommendation.
]
+ -
+
+ The additional directory /run in the root
+ file system is allowed. /run
+ replaces /var/run, and the
+ subdirectory /run/lock
+ replaces /var/lock, with
+ the /var directories replaced by symlinks
+ for backwards compatibility. /run
+ and /run/lock must follow all of the
+ requirements in the FHS for /var/run
+ and /var/lock, respectively, such as file
+ naming conventions, file format requirements, or the
+ requirement that files be cleared during the boot
+ process. Files and directories residing
+ in /run should be stored on a temporary
+ file system.
+
+
-
The following directories in the root filesystem are
- additionally allowed: /run,
-
- The purpose of the /run hierarchy is storage of ephemeral
- system state, that is, state information that should
- not be preserved across a reboot.
- Files and directories residing in /run
- should be stored on a temporary filesystem.
- The /run directory is a
- replacement for /var/run; its
- subdirectory /run/lock is a replacement for
- /var/lock.
- /run/ and /run/lock/ have been introduced
- by most distributions and are on track to be
- endorsed by the FHS.
- Additionally, the subdirectory /run/shm
- is a replacement for /dev/shm.
-
- /sys and /selinux.
-
- The /sys and /selinux
- directories are mount points where
- virtual filesystems are mounted which provide access
- to kernel information.
-
+ additionally allowed: /sys and
+ /selinux. These directories
+ are used as mount points to mount virtual filesystems
+ to get access to kernel information.
+
-
@@ -6407,6 +6415,29 @@ rmdir /usr/local/share/emacs 2>/dev/null || true
though the spool may still be physically located there.
+
+
+ /run and /run/lock
+
+
+ The directory /run is cleared at boot, normally
+ by being a mount point for a temporary file system. Packages
+ therefore must not assume that any files or directories
+ under /run other than /run/lock
+ exist unless the package has arranged to create those files or
+ directories since the last reboot. Normally, this is done by
+ the package via an init script. See [
+ for more information.
+ ]
+
+
+ Packages must not include files or directories
+ under /run, or under the
+ older /var/run and /var/lock paths.
+ The latter paths will normally be symlinks or other
+ redirections to /run for backwards compatibility.
+
+
@@ -6781,17 +6812,14 @@ test -f program-executed-later-in-script || exit 0
- Files and directories under /run, including those
- in directories /var/run and /var/lock
- which are symlinks or bind mounts to subdirectories of
- /run, are normally stored on a temporary
+ Files and directories under /run, including ones
+ referred to via the compatibility paths /var/run
+ and /var/lock, are normally stored on a temporary
filesystem and are normally not persistent across a reboot.
- Consequently, packages cannot assume that these files or
- directories are present at system boot time.
- Files and directories under /run must not be
- included in packages; such files or directories
- must be created dynamically, for example, in the
- init.d script.
+ The init.d scripts must handle this correctly.
+ This will typically mean creating any required subdirectories
+ dynamically when the init.d script is run.
+ See [ for more information.
]
@@ -7940,10 +7968,12 @@ fname () {
You may wish to restrict your script to SUSv3 features plus the
above set when possible so that it may use /bin/sh
- as its interpreter. If your script works with dash
- (originally called ash), it probably complies with
- the above requirements, but if you are in doubt, use
- /bin/bash.
+ as its interpreter. Checking your script
+ with checkbashisms from
+ the devscripts package or running your script
+ with posh may help uncover violations of the above
+ requirements. If in doubt whether a script complies with these
+ requirements, use /bin/bash.
@@ -9893,7 +9923,27 @@ END-INFO-DIR-ENTRY
You should not use the copyright file as a general README
file. If your package has such a file it should be
installed in /usr/share/doc/package/README or
- README.Debian or some other appropriate place.
+ README.Debian or some other appropriate place.
+
+
+
+ Machine-readable copyright information
+
+
+ A specification for a standard, machine-readable format
+ for debian/copyright files is maintained as part
+ of the debian-policy package. This
+ document may be found in the copyright-format
+ files in the debian-policy package. It is
+ also available from the Debian web mirrors at
+ .
+
+
+
+ Use of this format is optional.
+
+