X-Git-Url: https://git.donarmstrong.com/?p=debian%2Fdebian-policy.git;a=blobdiff_plain;f=policy.sgml;h=404dc7373f80cdc20bf793e064d7163e3885518f;hp=7bb703bef00b6767fe6eb064b7113c4b03f509b5;hb=HEAD;hpb=6271e034249125d29a5612d864a26f8bde1538ad diff --git a/policy.sgml b/policy.sgml index 7bb703b..404dc73 100644 --- a/policy.sgml +++ b/policy.sgml @@ -1931,6 +1931,10 @@ zope. any target that these targets depend on must also be non-interactive.
++ For packages in the main archive, no required targets + may attempt network access. +
The targets are as follows: @@ -2558,7 +2562,9 @@ Package: libc6 the field name is Package and the field value libc6.
- + Empty field values are only permitted in source package control files
+ (
A paragraph must not contain more than one instance of a
particular field name.
@@ -2701,6 +2707,7 @@ Package: libc6
file. These tools are responsible for removing the line
breaks from such fields when using fields from
@@ -7349,6 +7356,35 @@ rmdir /usr/local/share/emacs 2>/dev/null || true
+ This value must not be used, because it was
+ the error return sentinel value when uid_t
+ was 16 bits.
+
+ Dynamically allocated user accounts. By
+ default
+ (uid_t)(-2) == (gid_t)(-2) must not be
+ used, because it is used as the anonymous, unauthenticated
+ user by some NFS implementations.
+
(uid_t)(-1) == (gid_t)(-1) must
@@ -8891,6 +8927,7 @@ fname () {
would point to
@@ -10625,45 +10662,77 @@ END-INFO-DIR-ENTRY
- Any additional documentation that comes with the package may
- be installed at the discretion of the package maintainer.
- Plain text documentation should be installed in the directory
-
+ Plain text documentation should be compressed with gzip + -9 unless it is small. +
+ ++ If a package comes with large amounts of documentation that many + users of the package will not require, you should create a + separate binary package to contain it so that it does not take + up disk space on the machines of users who do not need or want + it installed. As a special case of this rule, shared library + documentation of any appreciable size should always be packaged + with the library development package () + or in a separate documentation package, since shared libraries + are frequently installed as dependencies of other packages by + users who have little interest in documentation of the library + itself. The documentation package for the + package package is conventionally + named package-doc + (or package-doc-language-code if there are + separate documentation packages for multiple languages). +
- If a package comes with large amounts of documentation which - many users of the package will not require you should create - a separate binary package to contain it, so that it does not - take up disk space on the machines of users who do not need - or want it installed.
+ Additional documentation included in the package should be + installed under
- It is often a good idea to put text information files
- (
Packages must not require the existence of any files in
@@ -10683,18 +10752,6 @@ END-INFO-DIR-ENTRY
- -
- Former Debian releases placed all additional documentation
- in
- If your package comes with extensive documentation in a
+ If the package comes with extensive documentation in a
markup format that can be converted to various other formats
you should if possible ship HTML versions in a binary
- package, in the directory
-