From: Manoj Srivastava Date: Thu, 16 Jun 2005 05:12:05 +0000 (+0000) Subject: * Improvements to section 7.1 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=d4c9ea4a5afdf4a15a3f2f6bcb477aecac716bf4;p=debian%2Fdebian-policy.git * Improvements to section 7.1 Author: jdg Date: 2001/04/30 00:13:43 * Improvements to section 7.1 git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-105 --- diff --git a/policy.sgml b/policy.sgml index f8de4ab..d59e64b 100644 --- a/policy.sgml +++ b/policy.sgml @@ -1467,7 +1467,7 @@ format.

- Syntax of control files + Syntax of control files

A control file consists of one or more paragraphs of fields. @@ -3088,7 +3088,7 @@ Declaring relationships between - packages + packages

Packages can declare in their control file that they have @@ -3100,9 +3100,10 @@

- This is done using the Depends, Recommends, - Suggests, Enhances, Conflicts, - Provides and Replaces control file fields. + This is done using the Depends, Pre-Depends, + Recommends, Suggests, Enhances, + Conflicts, Provides and Replaces + control file fields.

@@ -3113,7 +3114,7 @@

This is done using the Build-Depends, - Build-Depends-Indep, Build-Conflicts, and + Build-Depends-Indep, Build-Conflicts and Build-Conflicts-Indep control file fields.

@@ -3132,18 +3133,17 @@ control file fields of the package, which declare dependencies on other packages, the package names listed may also include lists of alternative package names, separated - by vertical bar symbols | (pipe symbols). In such - a case, the presence of any one of the alternative packages - is installed, that part of the dependency is considered to - be satisfied. + by vertical bar (pipe) symbols |. In such a case, + if any one of the alternative packages is installed, that + part of the dependency is considered to be satisfied.

- All the fields except Provides may restrict their - applicability to particular versions of each named package. - This is done in parentheses after each individual package - name; the parentheses should contain a relation from the - list below followed by a version number, in the format + All of the fields except for Provides may restrict + their applicability to particular versions of each named + package. This is done in parentheses after each individual + package name; the parentheses should contain a relation from + the list below followed by a version number, in the format described in .

@@ -3151,8 +3151,8 @@ The relations allowed are <<, <=, =, >= and >> for strictly earlier, earlier or equal, exactly equal, later or - equal and strictly later, respectively. The forms - < and > were used to mean + equal and strictly later, respectively. The deprecated + forms < and > were used to mean earlier/later or equal, rather than strictly earlier/later, so they should not appear in new packages (though dpkg still supports them). @@ -3160,22 +3160,23 @@

Whitespace may appear at any point in the version - specification, and must appear where it's necessary to + specification subject to the rules in , and must appear where it's necessary to disambiguate; it is not otherwise significant. For consistency and in case of future changes to dpkg it is recommended that a single space be used after a version relationship and before a version - number; it is usual also to put a single space after each - comma, on either side of each vertical bar, and before each - open parenthesis. + number; it is also conventional to put a single space after + each comma, on either side of each vertical bar, and before + each open parenthesis.

- For example: + For example, a list of dependencies might appear as: - Package: metamail - Version: 2.7-3 - Depends: libc5 (>= 5.2.18-4), mime-support, csh | tcsh + Package: mutt + Version: 1.3.17-1 + Depends: libc6 (>= 2.2.1), exim | mail-transport-agent

@@ -3184,7 +3185,7 @@ (Build-Depends, Build-Depends-Indep, Build-Conflicts and Build-Conflicts-Indep) may be restricted to a certain set of architectures. This - is done in brackets after each individual package name and + is indicated in brackets after each individual package name and the optional version specification. The brackets enclose a list of Debian architecture names separated by whitespace. Exclamation marks may be prepended to each of the names.