From 5a938bfca68e6f225bd23a4474fc5c8b95c7ace2 Mon Sep 17 00:00:00 2001 From: Manoj Srivastava Date: Thu, 16 Jun 2005 05:11:22 +0000 Subject: [PATCH] Improvements to chapter 3 Author: jdg Date: 2001/04/16 00:29:28 Improvements to chapter 3 git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-96 --- debconf_spec/debconf_specification.xml | 3 +- debian/changelog | 4 +- policy.sgml | 166 +++++++++++-------------- 3 files changed, 76 insertions(+), 97 deletions(-) diff --git a/debconf_spec/debconf_specification.xml b/debconf_spec/debconf_specification.xml index ce90d05..df14a87 100644 --- a/debconf_spec/debconf_specification.xml +++ b/debconf_spec/debconf_specification.xml @@ -10,7 +10,8 @@ Configuration management - revision 7.0 + Protocol version 2 + Revision 7.0 Wichert diff --git a/debian/changelog b/debian/changelog index c682fa6..27efcd4 100644 --- a/debian/changelog +++ b/debian/changelog @@ -16,10 +16,10 @@ debian-policy (3.5.3.0) unstable; urgency=low * [ACCEPTED 14/03/2001] Deprecate confusing closes: Bug#87828 Build-Depends arch syntax * [AMENDMENT 29/03/2001] Clarification of example closes: Bug#87711 - configuration files + configuration files * Undo all renaming to text, since the change had not been propogated to the rules file, which broke badly. This shall have to wait for a later - version. + version. -- Manoj Srivastava Sun, 15 Apr 2001 13:36:19 -0500 diff --git a/policy.sgml b/policy.sgml index 6ebe1fe..ac69418 100644 --- a/policy.sgml +++ b/policy.sgml @@ -1183,6 +1183,7 @@ Standards conformance +

In the source package's Standards-Version control @@ -1458,29 +1459,40 @@

Many of the tools in the package management suite manipulate - data in a common format, known as control files. Binary and - source packages have control data as do the .changes - files which control the installation of uploaded files, and - dpkg's internal databases are in a similar + data represented in a common format, known as control + data. The data is often stored in control + files. Binary and source packages have control files, + and the .changes files which control the installation + of uploaded files are also in control file format. + Dpkg's internal databases are in a similar format.

Syntax of control files

- A file consists of one or more paragraphs of fields. The - paragraphs are separated by blank lines. Some control files - only allow one paragraph; others allow several, in which - case each paragraph often refers to a different package. + A control file consists of one or more paragraphs of fields. + The paragraphs are separated by blank lines. Some control + files allow only one paragraph; others allow several, in + which case each paragraph usually refers to a different + package. (For example, in source packages, the first + paragraph refers to the source package, and later paragraphs + refer to binary packages generated from the source.)

- Each paragraph is a series of fields and values; each field - consists of a name, followed by a colon and the value. It - ends at the end of the line. Horizontal whitespace (spaces - and tabs) may occur immediately before or after the value - and is ignored there; it is conventional to put a single - space after the colon. + Each paragraph consists of a series of data fields; each + field consists of the field name, followed by a colon and + then the data/value associated with that field. It ends at + the end of the line. Horizontal whitespace (spaces and + tabs) may occur immediately before or after the value and is + ignored there; it is conventional to put a single space + after the colon. For example, a field might be: + + Package: libc6 + + the field name is Package and the field value + libc6.

@@ -1493,9 +1505,9 @@

Except where otherwise stated only a single line of data is allowed and whitespace is not significant in a field body. - Whitespace may never appear inside names (of packages, - architectures, files or anything else), version numbers or - in between the characters of multi-character version + Whitespace must not appear inside names (of packages, + architectures, files or anything else) or version numbers, + or between the characters of multi-character version relationships.

@@ -1510,21 +1522,12 @@ would mean a new paragraph.

-

- It is important to note that there are several fields which - are optional as far as dpkg and the related - tools are concerned, but which must appear in every Debian - package, or whose omission may cause problems. When writing - the control files for Debian packages you must read - the Debian policy manual in conjunction with the details - below and the list of fields for the particular file.

 List of fields

This list here is not supposed to be exhaustive. Most fields - are dealt with elsewhere in this document and in the - dpkg documentation. + are dealt with elsewhere in this document.

Package @@ -1537,10 +1540,10 @@

They must be at least two characters long and must start - with an alphanumeric character. The use of lowercase - package names is strongly recommended unless the package - you're building (or referring to, in other fields) is - already using uppercase.

+ with an alphanumeric character and not be all digits. The + use of lowercase package names is strongly recommended + unless the package you're building (or referring to, in + other fields) is already using uppercase.

 Version @@ -1563,12 +1566,9 @@ complies. This is updated manually when editing the source package to conform to newer standards; it can sometimes be used to tell when a package needs attention. + Its format is described above; see + .

- -

- Its format is the same as that of a version number except - that no epoch or Debian revision is allowed - see .

 @@ -1579,23 +1579,21 @@ In a .changes file or parsed changelog output this contains the (space-separated) name(s) of the distribution(s) where this version of the package should - be or was installed. Distribution names follow the rules - for package names. (See ). -

- -

+ be installed. Valid distributions are determined by the + archive maintainers. - Current distribution values are: + Current distribution names are: stable

This is the current `released' version of Debian - GNU/Linux. Once the - distribution is stable only major bug fixes - are allowed. When changes are made to this - distribution, the release number is increased - (for example: 1.2r1 becomes 1.2r2 then 1.2r3, etc). + GNU/Linux. Once the distribution is + stable only security fixes and other + major bug fixes are allowed. When changes are + made to this distribution, the release number is + increased (for example: 2.2r1 becomes 2.2r2 then + 2.2r3, etc).

@@ -1611,71 +1609,51 @@

+ testing + +

+ This distribution value refers to the + testing part of the Debian distribution + tree. It receives its packages from the + unstable distribution after a short time lag to + ensure that there are no major issues with the + unstable packages. It is less prone to breakage + than unstable, but still risky. It is not + possible to upload packages directly to + testing. +

+ + frozen

- From time to time, the unstable + From time to time, the frozen distribution enters a state of `code-freeze' in anticipation of release as a stable version. During this period of testing only fixes for existing or newly-discovered bugs will - be allowed. + be allowed. The exact details of this stage are + determined by the Release Manager.

experimental

- The packages with this distribution value are deemed - by their maintainers to be high risk. Oftentimes they - represent early beta or developmental packages from - various sources that the maintainers want people to - try, but are not ready to be a part of the other parts - of the Debian distribution tree. Download at your own + The packages with this distribution value are + deemed by their maintainers to be high + risk. Oftentimes they represent early beta or + developmental packages from various sources that + the maintainers want people to try, but are not + ready to be a part of the other parts of the + Debian distribution tree. Download at your own risk.

- There are several sections in each - distribution. Currently, these sections are: - - - main - -

- The packages in this section are those in the - main Debian distribution. They are all free - (according to the Debian free software - guidelines) and meet any other criteria for - inclusion described in this manual.

- - - contrib - -

- The packages in this section do not meet the - criteria for inclusion in the main Debian - distribution as defined by this manual, but are - otherwise free, as defined by the Debian free - software guidelines.

- - - non-free - -

- Packages in non-free do not meet the - criteria of free software, as defined by the - Debian free software guidelines. Again, use your - best judgment in downloading from this - Distribution.

- - You should list all distributions that - the package should be installed into. Except in unusual - circumstances, installations to stable should also - go into frozen (if it exists) and - unstable. Likewise, installations into - frozen should also go into unstable. + You should list all distributions that the + package should be installed into.

-- 2.39.5