From: Manoj Srivastava
- A Build-Depends on perl (>= 5.6.0-16) is - required. -
- In the absence of an explicit requirement,
- architecture-independent modules must depend on a minimum
-
+ These are the copyright dates of the original Policy manual. + Since then, this manual has been updated by many others. No + comprehensive collection of copyright notices for subsequent + work exists. +
+
This manual is free software; you may redistribute it and/or
modify it under the terms of the GNU General Public License
@@ -1985,6 +1992,12 @@
Field names are not case-sensitive, but it is usual to capitalize the field names using mixed case as shown below. + Field values are case-sensitive unless the description of the + field says otherwise.
@@ -2590,11 +2607,12 @@ Package: libc6
- Package names must consist only of lower case letters - (a-z), digits (0-9), plus (+) - and minus (-) signs, and periods (.). - They must be at least two characters long and must start - with an alphanumeric character. + Package names (both source and binary, + see ) must consist only of lower case + letters (a-z), digits (0-9), plus + (+) and minus (-) signs, and periods + (.). They must be at least two characters long and + must start with an alphanumeric character.
- Package names must consist only of lower case letters - (a-z), digits (0-9), plus (+) - and minus (-) signs, and periods (.). - They must be at least two characters long and must start - with an alphanumeric character. + Binary package names must follow the same syntax and + restrictions as source package names. See + for the details.
In the main
+ In the source package control file
Specifying any indicates that the source package
isn't dependent on any particular architecture and should
compile fine on any one. The produced binary package(s)
- will be specific to whatever the current build architecture
- is.
+ Specifying only all indicates that the source package + will only build architecture-independent packages. If this is + the case, all must be used rather than any; + any implies that the source package will build at + least one architecture-dependent package.
Specifying a list of architectures indicates that the source
will build an architecture-dependent package, and will only
- work correctly on the listed architectures.
@@ -2753,7 +2791,11 @@ Package: libc6
field lists the architecture(s) of the package(s)
currently being uploaded. This will be a list; if the
source for the package is also being uploaded, the special
- entry source is also present.
+ entry source is also present. all will be
+ present if any architecture-independent packages are being
+ uploaded. any may never occur in the
+ Architecture field in the
@@ -3061,18 +3103,16 @@ Package: libc6
- In a
- The part of the field before the first newline is empty; - thereafter each line has the name of a binary package and - the summary description line from that binary package. - Each line is indented by one space. -
-- You should list all distributions that the - package should be installed into. -
- -- More information is available in the Debian Developer's - Reference, section "The Debian archive". + Others are used for updating stable releases or for + security uploads. More information is available in the + Debian Developer's Reference, section "The Debian + archive".
- There should be nothing in this field before the first - newline; all the subsequent lines must be indented by at - least one space; blank lines must be represented by a line - consisting only of a space and a full stop. + The first line of the field value (the part on the same line + as Changes:) is always empty. The content of the + field is expressed as continuation lines, with each line + indented by at least one space. Blank lines must be + represented by a line consisting only of a space and a full + stop (.).
@@ -3257,29 +3262,27 @@ Package: libc6
- This field is a list of binary packages. + This field is a list of binary packages. Its syntax and + meaning varies depending on the control file in which it + appears.
- When it appears in the
- When it appears in a
- The syntax is a list of binary packages separated by
- commas
- This field appears in the control files of binary
- packages, and in the
- The disk space is represented in kilobytes as a simple - decimal number. + The disk space is given as the integer value of the estimated + installed size in bytes, divided by 1024 and rounded up.
@@ -3305,20 +3310,30 @@ Package: libc6This field contains a list of files with information about each one. The exact information and syntax varies with - the context. In all cases the part of the field - contents on the same line as the field name is empty. The - remainder of the field is one line per file, each line - being indented by one space and containing a number of - sub-fields separated by spaces. + the context. +
+ ++ In all cases, Files is a multiline field. The first line of + the field value (the part on the same line as Files:) + is always empty. The content of the field is expressed as + continuation lines, one line per file. Each line must be + indented by one space and contain a number of sub-fields, + separated by spaces, as described below.
In the
In the
@@ -4255,6 +4276,9 @@ Build-Depends: foo [!i386] | bar [!amd64] This is done using the Depends, Pre-Depends, Recommends, Suggests, Enhances, Breaks and Conflicts control file fields. + Breaks is described in , and + Conflicts is described in . The + rest are described below.
@@ -4442,12 +4466,6 @@ Build-Depends: foo [!i386] | bar [!amd64]
- Using Breaks may cause problems for upgrades from older
- versions of Debian and should not be used until the stable
- release of Debian supports Breaks.
-
When one binary package declares that it breaks another,
- Note that the same symbol (") is used for the left - and right quotation marks. A grave accent (`) is - not a quote character; neither is an apostrophe - ('). + Note that the same symbol (") is used + for the left and right quotation marks. A grave accent + (`) is not a quote character; neither is an + apostrophe (').
- Packages containing shared libraries that may be linked to
- by other packages' binaries, but which for some
- compelling reason can not be installed in
-
An ever increasing number of packages are using
@@ -8543,7 +8557,7 @@ name ["syshostname"]:
-
@@ -8576,54 +8590,35 @@ name ["syshostname"]:
- Packages using the X Window System should not be
- configured to install files under the
-
- Programs that use GNU
- The installation of files into subdirectories
- of
- Packages should install any relevant files into the
- directories
- These libraries used to be all symbolic
- links. However, with X11R7,
- /usr/include/X11 and /usr/lib/X11
- are now real directories, and packages
- should ship their files here instead
- of in /usr/X11R6/{include,lib}/X11.
- x11-common (>= 1:7.0.0) is the package
- responsible for converting these symlinks into
- directories.
-
- Due to limitations in current implementations, all characters
- in the manual page source should be representable in the usual
- legacy encoding for that language, even if the file is
- actually encoded in UTF-8. Safe alternative ways to write many
- characters outside that range may be found in
-
- Your package should call
- It is a good idea to specify a section for the location of
- your program; this is done with the --section
- switch. To determine which section to use, you should look
- at
- You should remove the entries in the
- If
+ Info documents should contain section and directory entry
+ information in the document for the use
+ of
-3.8.2.0 unreleased +3.8.3.0 Aug 2009 + + * Add DEB_*_ARCH_CPU and DEB_*_ARCH_OS variables and recommend them + over GNU-style variables for that information. [4.9] + * Source package Architecture fields may contain "all" in combination + with other architectures. Clarify when "all" and "any" may be used + in different versions of the field. [5.6.8] + * The Debian archive software does not support uploading to multiple + distributions with one *.changes file. [5.6.14] + * The Binary field may span multiple lines. [5.6.19] + * Remove the permission for shared library packages to install + libraries in a non-standard location and modify ld.so.conf. + Packages should either be installed in a standard library directory + or packages using them should be built with RPATH. [10.2] + * Clarify installation directories for X programs and remove the + requirement to pre-depend on x11-common before installing into + /usr/include/X11 and /usr/lib/X11. [11.8.7] + * Remove the requirement that all characters in a manual page be + representable in the legacy encoding for that language. [12.1] + * Localized man pages should either be kept up-to-date with the + original version or warn that they're not up-to-date, either with + warning text or by showing missing or changed portions in the + original language. [12.1] + * install-info is now handled via triggers so packages no longer need + to invoke it in maintainer scripts. Info documents should now have + directory sections and entries in the document. Packages + containing info documents should add a dependency to support + partial upgrades. [12.2] + * The requirement for Perl modules to have a versioned Depend and + Build-Depend on perl >= 5.6.0-16 has been removed. [perl] + +3.8.2.0 Jun 2009 * The list of archive sections has been significantly expanded. See http://lists.debian.org/debian-devel-announce/2009/03/msg00010.html @@ -50,6 +81,8 @@ picking your way through this list. * All packages must use debconf or equivalent for user prompting, though essential packages or their dependencies may also fall back on other methods. [3.9.1] + * The requirements for source package names are now explicitly + spelled out. [5.6.1] * Legacy XFree86 servers no longer get a special exception from the FHS permitting /etc/X11/XF86Config-4. [9.1] * Removed obsolete dependency requirements for packages that use @@ -58,8 +91,6 @@ picking your way through this list. starting in lenny. [11.8.5] * The GNU Free Documentation License version 1.3 is included in common-licenses and should be referenced from there. [12.5] - * The requirements for source package names are now explicitly - spelled out. [5.6.1] 3.8.1.0 Mar 2009