From: Manoj Srivastava Date: Thu, 16 Jun 2005 05:36:22 +0000 (+0000) Subject: fixed a typo noticed by Amos Shapira; slightly updated the verbiage to remove some... X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=169ddb19ec7d70074d186d3c217d1e8a284990c1;p=debian%2Fdebian-policy.git fixed a typo noticed by Amos Shapira; slightly updated the verbiage to remove some confusing redundancy in the same section Author: joy Date: 2003/02/05 14:24:31 fixed a typo noticed by Amos Shapira; slightly updated the verbiage to remove some confusing redundancy in the same section git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-176 --- diff --git a/policy.sgml b/policy.sgml index d73dc6f..e9684c8 100644 --- a/policy.sgml +++ b/policy.sgml @@ -7500,25 +7500,23 @@ name ["syshostname"]:

You should install manual pages in nroff source - form, in appropriate places under /usr/share/man. You - should only use sections 1 to 9 (see the FHS for more - details). You must not install a preformatted "cat - page".

+ form, in appropriate places under /usr/share/man. + You should only use sections 1 to 9 (see the FHS for more + details). You must not install a preformatted "cat page". +

Each program, utility, and function should have an - associated manpage included in the same package. It is + associated manual page included in the same package. It is suggested that all configuration files also have a manual - page included as well. + page included as well. Manual pages for protocols and other + auxiliary things are optional.

- There should be a manual page at for every program at the - very least, and possibly one for every configuration file, - protocol, utility, and function. If no manual page is - available, this is considered as a bug and should be - reported to the Debian Bug Tracking System (the maintainer - of the package is allowed to write this bug report + If no manual page is available, this is considered as a bug + and should be reported to the Debian Bug Tracking System (the + maintainer of the package is allowed to write this bug report themselves, if they so desire). Do not close the bug report until a proper manpage is available.