X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=5801b9015450cb1a707f64d3b425dc6494b719a4;hb=4d448b710fcdc52be791692c2d9ffb579cfb7d8e;hp=f9cb97043e390964f4680657a7b6b4598b778e19;hpb=f106831e1292e3a41589ff162edd02f8fb7c0dee;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index f9cb970..5801b90 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -1113,7 +1113,7 @@
file in their control archive. The
@@ -3773,7 +3773,7 @@ Replaces: mail-transport-agent
libraries that are needed by libbar are linked
indirectly to foo, and the dynamic
linker will load them automatically when it loads
- libbar. A package should needs to depend on
+ libbar. A package should depend on
the libraries it directly uses, and the dependencies for
those libraries should automatically pull in the other
libraries.
@@ -4138,16 +4138,20 @@ libbar 1 bar1 (>= 1.0-1)
The location of all installed files and directories must
comply with the Filesystem Hierarchy Standard (FHS),
- except where doing so would violate other terms of Debian
- Policy. The latest version of this document can be found
- in the debian-policy package or on
+ version 2.1, except where doing so would violate other
+ terms of Debian Policy. The version of this document
+ referred here can be found in the debian-policy
+ package or on
- The /etc/init.d scripts should be treated as - configuration files, either by marking them as - conffiles or managing them correctly in the - maintainer scripts (see ). This is - important since we want to give the local system - administrator the chance to adapt the scripts to the local - system, e.g., to disable a service without de-installing - the package, or to specify some special command line - options when starting a service, while making sure her - changes aren't lost during the next package upgrade. + The /etc/init.d scripts must be treated as + configuration files, either (if they are present in the + package, that is, in the .deb file) by marking them as + conffiles, or, (if they do not exist in the .deb) + by managing them correctly in the maintainer scripts (see + ). This is important since we want + to give the local system administrator the chance to adapt + the scripts to the local system, e.g., to disable a + service without de-installing the package, or to specify + some special command line options when starting a service, + while making sure her changes aren't lost during the next + package upgrade.