X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=404dc7373f80cdc20bf793e064d7163e3885518f;hb=8923e883eaadc169a6b12dd84c1d64927201f237;hp=947a1e1561e4d80d3435c00103d8cbee8e05d1b2;hpb=b083c75f46a06d37393214ab94c7f5d6e698a0c4;p=debian%2Fdebian-policy.git diff --git a/policy.sgml b/policy.sgml index 947a1e1..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
@@ -10655,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
-
- 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.
+ Plain text documentation should be compressed with gzip + -9 unless it is small. +
- It is often a good idea to put text information files
- (
+ Additional documentation included in the package should be
+ installed under
+ Any separate package providing documentation must still install
+ standard documentation files in its
+ own
Packages must not require the existence of any files in
@@ -10713,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
-