In addition to the main technical manual, the team currently also maintains:
-+ [[http://www.debian.org/doc/packaging-manuals/copyright-format/1.0][Machine-readable debian/copyright format]]
++ [[http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/][Machine-readable debian/copyright format]]
+ [[http://www.debian.org/doc/packaging-manuals/menu-policy/][Debian Menu sub-policy]]
+ [[http://www.debian.org/doc/packaging-manuals/perl-policy/][Debian Perl Policy]]
+ [[http://www.debian.org/doc/packaging-manuals/mime-policy/][Debian MIME support sub-policy]]
standard, machine-readable format for
<filename>debian/copyright</filename> files within packages and
facilitate automated checking and reporting of licenses for packages and
- sets of packages. The DEP drivers were Steve Langasek
- <email>vorlon@debian.org</email> and Lars Wirzenius
- <email>liw@liw.fi</email>.
+ sets of packages.
</para>
</abstract>
</articleinfo>
A white space separated list means that the field value may be on one
line or many, but values in the list are separated by one or more white
space characters (including space, TAB, and newline). For example, the
- <varname>Files</varname>field has a list of filename patterns.
+ <varname>Files</varname> field has a list of filename patterns.
</para>
</section>
<title><varname>Format</varname></title>
<para>
Required single line: URI of the format specification, such as:
- <literal>http://www.debian.org/doc/copyright-format/1.0</literal>
+ <literal>http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/</literal>
</para>
</section>
package, for instance when a work combines a permissive and a copyleft
license, or to document a <emphasis>compilation copyright</emphasis>
and license. It is possible to use only <varname>License</varname> in
- the header paragraph, but <varname>Copyright</varname>alone makes no
+ the header paragraph, but <varname>Copyright</varname> alone makes no
sense.
</para>
</section>
<section id="example-header-paragraph">
<title>Example header paragraph</title>
-<programlisting>Format: <VERSIONED_FORMAT_URL>
+<programlisting>Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: SOFTware
Upstream-Contact: John Doe <john.doe@example.com>
Source: http://www.example.com/software/project</programlisting>
[LICENSE TEXT]
License: LGPL-2.1
- LICENSE TEXT]</programlisting>
+ [LICENSE TEXT]</programlisting>
</example>
<example>
</para>
<para>
Currently, the full text of the licenses is only available in the <ulink
- url="http://spdx.org/wiki/working-version-license-list">working version
- of the SPDX license list</ulink>.
+ url="http://spdx.org/licenses">SPDX Open Source License Registry</ulink>.
</para>
<informaltable>
<tgroup cols="2">
</entry>
<entry>
Apache license
- <ulink url="http://spdx.org/licenses/ASL-1.0">1.0</ulink>,
- <ulink url="http://spdx.org/licenses/ASL-2.0">2.0</ulink>.
+ <ulink url="http://spdx.org/licenses/Apache-1.0">1.0</ulink>,
+ <ulink url="http://spdx.org/licenses/Apache-2.0">2.0</ulink>.
</entry>
</row>
<row>
CC0
</entry>
<entry>
- Creative Commons <ulink
- url="http://creativecommons.org/license/zero/">Universal
- waiver</ulink>.
+ Creative Commons Zero 1.0 Universal
+ <ulink url="http://spdx.org/licenses/CC0-1.0">1.0</ulink>.
</entry>
</row>
<row>
CDDL
</entry>
<entry>
- <ulink url="http://spdx.org/licenses/CDDL">Common Development
- and Distribution License</ulink>.
+ Common Development and Distribution License
+ <ulink url="http://spdx.org/licenses/CDDL-1.0">1.0</ulink>.
</entry>
</row>
<row>
</entry>
<entry>
The Eiffel Forum License
- <ulink url="http://spdx.org/licenses/EPL-1.0">1.0</ulink>.
+ <ulink url="http://spdx.org/licenses/EFL-1.0">1.0</ulink>,
+ <ulink url="http://spdx.org/licenses/EFL-2.0">2.0</ulink>.
</entry>
</row>
<row>
<ulink url="http://spdx.org/licenses/LGPL-2.1">2.1</ulink>,
<ulink url="http://spdx.org/licenses/LGPL-3.0">3.0</ulink>, or
GNU Library General Public License
- <ulink url="http://spdx.org/licenses/LGPL-1.0">1.0</ulink>,
<ulink url="http://spdx.org/licenses/LGPL-2.0">2.0</ulink>.
</entry>
</row>
GFDL
</entry>
<entry>
- <ulink url="http://spdx.org/licenses/FDL-1.0">GNU Free
- Documentation License</ulink>.
+ GNU Free Documentation License 1.0, or
+ <ulink url="http://spdx.org/licenses/GFDL-1.1">1.1</ulink>.
</entry>
</row>
<row>
</row>
<row>
<entry>
- Python-CNRI
+ Python
</entry>
<entry>
- <ulink url="http://spdx.org/licenses/Python-CNRI">Python
- license</ulink>.
+ Python license
+ <ulink url="http://spdx.org/licenses/Python-2.0">2.0</ulink>.
</entry>
+ <!-- See https://fossbazaar.org/pipermail/spdx-legal/2011-February/000010.html -->
</row>
<row>
<entry>
Zope
</entry>
<entry>
- Zope Public License
- <ulink url="http://spdx.org/licenses/ZPL-1.0">1.0</ulink>,
+ Zope Public License 1.0,
+ <ulink url="http://spdx.org/licenses/ZPL-1.1">1.1</ulink>,
<ulink url="http://spdx.org/licenses/ZPL-2.0">2.0</ulink>,
<ulink url="http://spdx.org/licenses/ZPL-2.1">2.1</ulink>.
</entry>
matches.
</para>
<para>
- Exceptions and clarifications are signaled in plain text, by appending
+ An exception or clarification to a license is signaled in plain text, by appending
<literal>with <varname><replaceable>keywords</replaceable></varname>
exception</literal> to the short name. This document provides a list of
- keywords that refer to the most frequent exceptions.
+ keywords that must be used when referring to the most frequent
+ exceptions. When exceptions other than these are in effect that modify
+ a common license by granting additional permissions, you may use an
+ arbitrary keyword not taken from the below list of keywords. When a
+ license differs from a common license because of added restrictions
+ rather than because of added permissions, a distinct short name should
+ be used instead of <literal>with
+ <varname><replaceable>keywords</replaceable></varname>exception</literal>.
+ </para>
+ <para>
+ Only one exception may be specified for each license within a given
+ license specification. If more than one exception applies to a single
+ license, an arbitrary short name must be used instead.
</para>
<para>
The GPL <literal>Font</literal> exception refers to the text added to the
A possible <filename>debian/copyright</filename> file for the program
<quote>X Solitaire</quote> distributed in the Debian source package
<literal>xsol</literal>:
-<programlisting><![CDATA[Format: <VERSIONED_FORMAT_URL>
+<programlisting><![CDATA[Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: X Solitaire
Source: ftp://ftp.example.com/pub/games
Files: debian/*
Copyright: Copyright 1998 Jane Smith <jsmith@example.net>
-License:
+License: GPL-2+
[LICENSE TEXT]]]></programlisting>
</para>
</example>
A possible <filename>debian/copyright</filename> file for the program
<quote>Planet Venus</quote>, distributed in the Debian source
package <literal>planet-venus</literal>:
-<programlisting><![CDATA[Format: <VERSIONED_FORMAT_URL>
+<programlisting><![CDATA[Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: Planet Venus
Upstream-Contact: John Doe <jdoe@example.com>
Source: http://www.example.com/code/venus
Files: debian/*
Copyright: 2008, Dan Developer <dan@debian.example.com>
-License:
+License: permissive
Copying and distribution of this package, with or without
modification, are permitted in any medium without royalty
provided the copyright notice and this notice are
</example>
</section>
- <section id="appendix">
- <title>
- Appendix: Note about the use of this format in Debian
- </title>
- <para>
- The Debian Policy (§<ulink
- url="http://www.debian.org/doc/debian-policy/ch-docs#s-copyrightfile">12.5</ulink>)
- demands that each package is accompanied by a file,
- <filename>debian/copyright</filename> in source packages and
- <filename>/usr/share/doc/package/copyright</filename> in binary packages,
- that contains a verbatim copy of its copyright and distribution license.
- In addition, it requires that copyrights must be extractable by mechanical
- means. This proposal for machine-readable copyright and license summary
- files has been crafted for Debian's use, but it is our hope that other
- software distributions, as well as upstream developers will adopt it, so
- that review efforts can be easily reproduced and shared.
- </para>
- <para>
- The copyright of the Debian packaging and the history of package
- maintainers is simply indicated in a <literal>Files: debian/*</literal>
- paragraph.
- </para>
- </section>
</article>
-debian-policy (3.9.2.1) UNRELEASED; urgency=low
+debian-policy (3.9.3.0) UNRELEASED; urgency=low
+ [ Russ Allbery ]
+ * Policy: Improve Architecture field in source package
+ Wording: Raphaël Hertzog <hertzog@debian.org>
+ Seconded: Russ Allbery <rra@debian.org>
+ Seconded: Charles Plessy <plessy@debian.org>
+ Seconded: Guillem Jover <guillem@debian.org>
+ Closes: #626779
+ * Policy: Initial Debian maintainers need not be listed in copyright
+ Wording: Charles Plessy <plessy@debian.org>
+ Seconded: Russ Allbery <rra@debian.org>
+ Seconded: Raphaël Hertzog <hertzog@debian.org>
+ Seconded: Andrew McMillan <andrew@morphoss.com>
+ Closes: #593533
+ * Policy: Document cron job file naming restrictions
+ Wording: Karl E. Jorgensen <karl@jorgensen.org.uk>
+ Wording: Russ Allbery <rra@debian.org>
+ Seconded: Russ Allbery <rra@debian.org>
+ Seconded: Dominic Hargreaves <dom@earth.li>
+ Seconded: Javier Fernández-Sanguino Peña <jfs@computer.org>
+ Closes: #609162
+ * Consistently use "Debian source control file" for *.dsc files and
+ "Source package control file" for debian/control files. Patch from
+ Charles Plessy. (Closes: #626796)
+ * Clarify that continuation lines of the Description control field must
+ contain at least one non-whitespace character. Thanks, Guillem Jover.
+ (Closes: #627490)
+ * Fix the example of creating a /usr/local subdirectory to not fail if
+ the chown or chmod fail. Thanks, Joey Hess. (Closes: #617315)
+ * Clarify the requirements for symlinks from inside one top-level
+ directory to another and add examples and a rationale. Thanks,
+ Carsten Hey. (Closes: #626338)
+ * Clarify that Perl Policy 2.4 is for packages built from the perl
+ source package and the manual page extensions are different for
+ separate module packages. Thanks, Steve Langasek. (Closes: #643690)
+ * Say that packages in main may also not recommend packages in non-free,
+ bringing the main text in line with the list of fields and in line
+ with the long-standing release goal. (Closes: #646166)
+ * Resynchronize the archive section list with ftp-master, adding
+ education, introspection, and metapackages. Patch from Charles
+ Plessy. (Closes: #651020)
* Add the release date of 3.9.2.0 to upgrading-checklist.
* Fix ordering of the last entries in the 3.9.2.0 upgrading-checklist.
* Fix typo in upgrading-checklist entry for multiarch paths. Thanks,
- Michael Dorrington.
+ Michael Dorrington. (Closes: #626408)
+ * Add id tags for each version entry in upgrading-checklist so that,
+ when eventually published somewhere, other Debian web sites can link
+ to specific entries. Patch from Charles Plessy.
+ * Add AGPL-3 to tools/license-count.
+ * Add build-arch and build-indep targets to debian/rules.
+
+ [ Bill Allombert ]
+ * Policy: Link relationship fields (7.1) to architecture specification
+ strings (11.1).
+ Patch from Charles Plessy in #628174.
+ * Policy: Retire legacy Motif policy (11.8.8)
+ Proposed by: Justin B Rye
+ Wording: Russ Allbery <rra@debian.org>
+ Seconded: Jakub Wilk <jwilk@debian.org>
+ Seconded: Steve Langasek <vorlon@debian.org>
+ Seconded: Charles Plessy <plessy@debian.org>
+ Closes: #621479
+ * copyright-format: Fix URL for the Eiffel Forum License.
+ Reported by Thomas Preud'homme, patch by Charles Plessy.
+ Closes: #623050
+ * copyright-format: Update SPDX link to point to the SPDX license registry.
+ Patch by Charles Plessy. Closes: #628540
+ * copyright-format: Correct or add links to SPDX.
+ Wording: Charles Plessy <plessy@debian.org>
+ Seconded: Gregor Herrmann <gregoa@debian.org>
+ Closes: #641071
+ * Policy: Clarify that 'machine-extractable' referer the copyright
+ files (12.5)
+ Wording: Charles Plessy <plessy@debian.org>
+ Seconded: Bill Allombert <ballombe@debian.org>
+ Seconded: Jakub Wilk <jwilk@debian.org>
+ Closes: #617516
+ * copyright-format: remove drivers from abstract and useless appendix
+ Wording: Lars Wirzenius <liw@liw.fi>
+ Seconded: Charles Plessy <plessy@debian.org>
+ Seconded: Jakub Wilk <jwilk@debian.org>
+ Closes: #640735
+ * copyright-format: Fix syntax of examples.
+ Proposed by: Charles Plessy <plessy@debian.org>
+ Wording: Jonathan Nieder <jrnieder@gmail.com>
+ Closes: #649674
+ * copyright-format: Clarify specification of multiple license exception:
+ Wording: Steve Langasek <vorlon@debian.org>
+ Seconded: Craig Small <csmall@debian.org>
+ Seconded: Gregor Herrmann <gregoa@debian.org>
+ Seconded: Jakub Wilk <jwilk@debian.org>
+ Seconded: Jonas Smedegaard <dr@jones.dk>
+ Closes: #633797
+ * copyright-format: Specify URL on www.debian.org
+ Wording: Charles Plessy <plessy@debian.org>
+ Seconded: David Prévot <taffit@debian.org>
+ Seconded: Gregor Herrmann <gregoa@debian.org>
+ Closes: #640737
+ * Perl policy: Document major version upgrade trigger
+ Wording: Dominic Hargreaves <dom@debian.org>
+ Seconded: Russ Allbery <rra@debian.org>
+ Seconded: Niko Tyni <ntyni@debian.org>
+ Seconded: Gregor Herrmann <gregoa@debian.org>
+ Closes: #619275
+ * Virtual: change ttf-japanese-{mincho, gothic} to
+ fonts-japanese-{mincho, gothic}.
+ Proposed by: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
+ Seconded: Charles Plessy <plessy@debian.org>
+ Seconded: Bill Allombert <ballombe@debian.org>
+ Closes: #644230
+ * Policy 9.10: No more recommend to call install-docs for doc-base.
+ Wording: Charles Plessy <plessy@debian.org>
+ Seconded: Robert Luberda <robert@debian.org>
+ Seconded: Raphael Hertzog <hertzog@debian.org>
+ Closes: #637614
- -- Russ Allbery <rra@debian.org> Wed, 06 Apr 2011 23:04:37 -0700
+ -- Bill Allombert <ballombe@debian.org> Wed, 30 Nov 2011 22:27:54 +0100
debian-policy (3.9.2.0) unstable; urgency=low
make_directory := install -p -d -o root -g root -m 755
-all build: stamp-build
+all build build-indep: stamp-build
+build-arch:
stamp-build: version.ent $(sanitycheck)
$(MAKE) $(SGML_FILES:=.sgml.validate) \
$(SGML_FILES:=.html.tar.gz) \
touch stamp-policy
-.PHONY: configure build binary binary-arch binary-indep clean checkroot
+.PHONY: configure build build-arch build-indep binary binary-arch
+.PHONY: binary-indep clean checkroot
#Local variables:
#mode: makefile
package.
</p>
<p>
- Manual pages distributed with Perl packages must be installed
- into the standard directories:
+ Manual pages distributed with packages built from the perl
+ source package must be installed into the standard directories:
<taglist>
<tag>Programs</tag>
<item>
</p>
</item>
</taglist>
+ The extensions used for manual pages distributed with module
+ packages are different. See <ref id="vendor_dirs">.
</p>
</sect>
</chapt>
package must depend upon it explicitly.
</p>
</sect>
+
+ <sect id="perl_upgrades">
+ <heading>Perl Package Upgrades</heading>
+ <p>
+ Starting from <package>perl</package> 5.12.3-2, a dpkg trigger
+ named <var>perl-major-upgrade</var> will be triggered by the
+ postinst of the <package>perl</package> package during major
+ upgrades. Some examples of things which constitute a major upgrade
+ are an upgrade which would change the value of versioned
+ directories in <tt>@INC</tt>, or one which changes <tt>abiname</tt>.
+ Any package may declare an interest in the trigger, especially
+ packages including long-running daemons which would stop working
+ until restart.
+ </p>
+ <p>
+ It is suggested that such packages include an appropriate section
+ in their postinst to handle the trigger by restarting relevant
+ daemons or notifying users of further action.
+ </p>
+ </sect>
</chapt>
<appendix id="perl6">
In addition, the packages in <em>main</em>
<list compact="compact">
<item>
- must not require a package outside of <em>main</em>
- for compilation or execution (thus, the package must
- not declare a "Depends", "Recommends", or
+ must not require or recommend a package outside
+ of <em>main</em> for compilation or execution (thus, the
+ package must not declare a "Depends", "Recommends", or
"Build-Depends" relationship on a non-<em>main</em>
package),
</item>
list of sections. At present, they are:
<em>admin</em>, <em>cli-mono</em>, <em>comm</em>, <em>database</em>,
<em>devel</em>, <em>debug</em>, <em>doc</em>, <em>editors</em>,
- <em>electronics</em>, <em>embedded</em>, <em>fonts</em>,
- <em>games</em>, <em>gnome</em>, <em>graphics</em>, <em>gnu-r</em>,
- <em>gnustep</em>, <em>hamradio</em>, <em>haskell</em>,
- <em>httpd</em>, <em>interpreters</em>, <em>java</em>, <em>kde</em>,
- <em>kernel</em>, <em>libs</em>, <em>libdevel</em>, <em>lisp</em>,
- <em>localization</em>, <em>mail</em>, <em>math</em>, <em>misc</em>,
+ <em>education</em>, <em>electronics</em>, <em>embedded</em>,
+ <em>fonts</em>, <em>games</em>, <em>gnome</em>, <em>graphics</em>,
+ <em>gnu-r</em>, <em>gnustep</em>, <em>hamradio</em>, <em>haskell</em>,
+ <em>httpd</em>, <em>interpreters</em>, <em>introspection</em>,
+ <em>java</em>, <em>kde</em>, <em>kernel</em>, <em>libs</em>,
+ <em>libdevel</em>, <em>lisp</em>, <em>localization</em>,
+ <em>mail</em>, <em>math</em>, <em>metapackages</em>, <em>misc</em>,
<em>net</em>, <em>news</em>, <em>ocaml</em>, <em>oldlibs</em>,
<em>otherosfs</em>, <em>perl</em>, <em>php</em>, <em>python</em>,
<em>ruby</em>, <em>science</em>, <em>shells</em>, <em>sound</em>,
lines. The first line of the value, the part on the same line as
the field name, often has special significance or may have to be
empty. Other lines are added following the same syntax as the
- continuation lines the folded fields. Whitespace, including newlines,
+ continuation lines of the folded fields. Whitespace, including newlines,
is significant in the values of multiline fields.
</item>
</taglist>
</p>
<p>
- The source package control file is generated by
+ The Debian source control file is generated by
<prgn>dpkg-source</prgn> when it builds the source
archive, from other files in the source package,
described above. When unpacking, it is checked against
</p>
<p>
- In the source package control file <file>.dsc</file>, this
- field may contain either the architecture
- wildcard <tt>any</tt> or a list of architectures and
- architecture wildcards separated by spaces. If a list is
- given, it may include (or consist solely of) the special
+ In the Debian source control file <file>.dsc</file>, this
+ field contains a list of architectures and architecture
+ wildcards separated by spaces. When the list contains the
+ architecture wildcard <tt>any</tt>, the only other value
+ allowed in the list is <tt>all</tt>.
+ </p>
+
+ <p>
+ The list may include (or consist solely of) the special
value <tt>all</tt>. In other words, in <file>.dsc</file>
files unlike the <file>debian/control</file>, <tt>all</tt> may
occur in combination with specific architectures.
- The <tt>Architecture</tt> field in the source package control
+ The <tt>Architecture</tt> field in the Debian source control
file <file>.dsc</file> is generally constructed from
the <tt>Architecture</tt> fields in
the <file>debian/control</file> in the source package.
</p>
<p>
- Specifying <tt>any</tt> indicates that the source package
+ Specifying only <tt>any</tt> 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 either be specific to whatever the current build
- architecture is or will be architecture-independent.
+ will be specific to whatever the current build architecture is.
</p>
<p>
Specifying only <tt>all</tt> indicates that the source package
- will only build architecture-independent packages. If this is
- the case, <tt>all</tt> must be used rather than <tt>any</tt>;
- <tt>any</tt> implies that the source package will build at
- least one architecture-dependent package.
+ will only build architecture-independent packages.
+ </p>
+
+ <p>
+ Specifying <tt>any all</tt> indicates that the source package
+ isn't dependent on any particular architecture. The set of
+ produced binary packages will include at least one
+ architecture-dependant package and one architecture-independent
+ package.
</p>
<p>
Those starting with a single space are part of a paragraph.
Successive lines of this form will be word-wrapped when
displayed. The leading space will usually be stripped off.
+ The line must contain at least one non-whitespace character.
</item>
<item>
will be allowed to trail off to the right. None, one or two
initial spaces may be deleted, but the number of spaces
deleted from each line will be the same (so that you can have
- indenting work correctly, for example).
+ indenting work correctly, for example). The line must
+ contain at least one non-whitespace character.
</item>
<item>
Additional user-defined fields may be added to the
source package control file. Such fields will be
ignored, and not copied to (for example) binary or
- source package control files or upload control files.
+ Debian source control files or upload control files.
</p>
<p>
field name after the hyphen will be used in the output
file. Where the letter <tt>B</tt> is used the field
will appear in binary package control files, where the
- letter <tt>S</tt> is used in source package control
+ letter <tt>S</tt> is used in Debian source control
files and where <tt>C</tt> is used in upload control
(<tt>.changes</tt>) files.
</p>
<example>
XBS-Comment: I stand between the candle and the star.
</example>
- then the binary and source package control files will contain the
+ then the binary and Debian source control files will contain the
field
<example>
Comment: I stand between the candle and the star.
architectures. This is indicated in brackets after each
individual package name and the optional version specification.
The brackets enclose a list of Debian architecture names
+ in the format described in <ref id="arch-spec">,
separated by whitespace. Exclamation marks may be prepended to
each of the names. (It is not permitted for some names to be
prepended with exclamation marks while others aren't.)
<p>
Relationships may also be restricted to a certain set of
- architectures using architecture wildcards. The syntax for
+ architectures using architecture wildcards in the format
+ described in <ref id="arch-wildcard-spec">. The syntax for
declaring such restrictions is the same as declaring
restrictions using a certain set of architectures without
architecture wildcards. For example:
For example, the <tt>emacsen-common</tt> package could
contain something like
<example compact="compact">
-if [ ! -e /usr/local/share/emacs ]
-then
- if mkdir /usr/local/share/emacs 2>/dev/null
- then
- chown root:staff /usr/local/share/emacs
- chmod 2775 /usr/local/share/emacs
+if [ ! -e /usr/local/share/emacs ]; then
+ if mkdir /usr/local/share/emacs 2>/dev/null; then
+ if chown root:staff /usr/local/share/emacs; then
+ chmod 2775 /usr/local/share/emacs || true
+ fi
fi
fi
</example>
</p>
</sect>
- <sect>
+ <sect id="cron-jobs">
<heading>Cron jobs</heading>
<p>
Packages must not modify the configuration file
<file>/etc/crontab</file>, and they must not modify the files in
- <file>/var/spool/cron/crontabs</file>.</p>
+ <file>/var/spool/cron/crontabs</file>.
+ </p>
<p>
- If a package wants to install a job that has to be executed
- via cron, it should place a file with the name of the
- package in one or more of the following directories:
+ If a package wants to install a job that has to be executed via
+ cron, it should place a file named as specified
+ in <ref id="cron-files"> into one or more of the following
+ directories:
<example compact="compact">
/etc/cron.hourly
/etc/cron.daily
As these directory names imply, the files within them are
executed on an hourly, daily, weekly, or monthly basis,
respectively. The exact times are listed in
- <file>/etc/crontab</file>.</p>
+ <file>/etc/crontab</file>.
+ </p>
<p>
All files installed in any of these directories must be
<p>
If a certain job has to be executed at some other frequency or
- at a specific time, the package should install a file
- <file>/etc/cron.d/<var>package</var></file>. This file uses the
- same syntax as <file>/etc/crontab</file> and is processed by
- <prgn>cron</prgn> automatically. The file must also be
+ at a specific time, the package should install a file in
+ <file>/etc/cron.d</file> with a name as specified
+ in <ref id="cron-files">. This file uses the same syntax
+ as <file>/etc/crontab</file> and is processed
+ by <prgn>cron</prgn> automatically. The file must also be
treated as a configuration file. (Note that entries in the
<file>/etc/cron.d</file> directory are not handled by
<prgn>anacron</prgn>. Thus, you should only use this
directory for jobs which may be skipped if the system is not
- running.)</p>
+ running.)
+ </p>
+
<p>
Unlike <file>crontab</file> files described in the IEEE Std
1003.1-2008 (POSIX.1) available from
execute scripts in
<file>/etc/cron.{hourly,daily,weekly,monthly}</file>.
</p>
+
+ <sect1 id="cron-files">
+ <p>
+ The file name of a cron job file should normally match the
+ name of the package from which it comes.
+ </p>
+
+ <p>
+ If a package supplies multiple cron job files files in the
+ same directory, the file names should all start with the name
+ of the package (possibly modified as described below) followed
+ by a hyphen (<tt>-</tt>) and a suitable suffix.
+ </p>
+
+ <p>
+ A cron job file name must not include any period or plus
+ characters (<tt>.</tt> or <tt>+</tt>) characters as this will
+ cause cron to ignore the file. Underscores (<tt>_</tt>)
+ should be used instead of <tt>.</tt> and <tt>+</tt>
+ characters.
+ </p>
+ </sect1>
</sect>
<sect id="menus">
package that provides online documentation (other than just
manual pages) to register these documents with
<package>doc-base</package> by installing a
- <package>doc-base</package> control file via the
- <prgn/install-docs/ script at installation time and
- de-register the manuals again when the package is removed.
+ <package>doc-base</package> control file in
+ <file>/usr/share/doc-base/</file>.
</p>
<p>
Please refer to the documentation that comes with the
<heading>Symbolic links</heading>
<p>
- In general, symbolic links within a top-level directory
- should be relative, and symbolic links pointing from one
- top-level directory into another should be absolute. (A
- top-level directory is a sub-directory of the root
- directory <file>/</file>.)
+ In general, symbolic links within a top-level directory should
+ be relative, and symbolic links pointing from one top-level
+ directory to or into another should be absolute. (A top-level
+ directory is a sub-directory of the root
+ directory <file>/</file>.) For example, a symbolic link
+ from <file>/usr/lib/foo</file> to <file>/usr/share/bar</file>
+ should be relative (<file>../share/bar</file>), but a symbolic
+ link from <file>/var/run</file> to <file>/run</file> should be
+ absolute.<footnote>
+ This is necessary to allow top-level directories to be
+ symlinks. If linking <file>/var/run</file>
+ to <file>/run</file> were done with the relative symbolic
+ link <file>../run</file>, but <file>/var</file> were a
+ symbolic link to <file>/srv/disk1</file>, the symbolic link
+ would point to <file>/srv/run</file> rather than the intended
+ target.
+ </footnote>
</p>
<p>
policy (such as for <ref id="appdefaults">).
</p>
</sect1>
-
- <sect1>
- <heading>The OSF/Motif and OpenMotif libraries</heading>
-
- <p>
- <em>Programs that require the non-DFSG-compliant OSF/Motif or
- OpenMotif libraries</em><footnote>
- OSF/Motif and OpenMotif are collectively referred to as
- "Motif" in this policy document.
- </footnote>
- should be compiled against and tested with LessTif (a free
- re-implementation of Motif) instead. If the maintainer
- judges that the program or programs do not work
- sufficiently well with LessTif to be distributed and
- supported, but do so when compiled against Motif, then two
- versions of the package should be created; one linked
- statically against Motif and with <tt>-smotif</tt>
- appended to the package name, and one linked dynamically
- against Motif and with <tt>-dmotif</tt> appended to the
- package name.
- </p>
-
- <p>
- Both Motif-linked versions are dependent
- upon non-DFSG-compliant software and thus cannot be
- uploaded to the <em>main</em> distribution; if the
- software is itself DFSG-compliant it may be uploaded to
- the <em>contrib</em> distribution. While known existing
- versions of Motif permit unlimited redistribution of
- binaries linked against the library (whether statically or
- dynamically), it is the package maintainer's
- responsibility to determine whether this is permitted by
- the license of the copy of Motif in their possession.
- </p>
- </sect1>
</sect>
<sect id="perl">
<p>
In addition, the copyright file must say where the upstream
- sources (if any) were obtained. It should name the original
- authors of the package and the Debian maintainer(s) who were
- involved with its creation.
+ sources (if any) were obtained, and should name the original
+ authors.
</p>
<p>
<file>/usr/share/doc/<var>package</var></file> may be a symbolic
link to another directory in <file>/usr/share/doc</file> only if
the two packages both come from the same source and the
- first package Depends on the second. These rules are
- important because copyrights must be extractable by
+ first package Depends on the second. These rules are important
+ because <file>copyright</file> files must be extractable by
mechanical means.
</p>
<!-- Local variables: -->
<!-- indent-tabs-mode: t -->
<!-- End: -->
-<!-- vim:set ai et sts=2 sw=2 tw=76: -->
+<!-- vim:set ai sts=2 sw=2 tw=76: -->
[qr,/usr/share/common-licenses/GPL, => 'GPL (any)'],
[qr,/usr/share/common-licenses/LGPL, => 'LGPL (any)'],
+ [qr,(?m)^License:.*AGPL-3, => 'AGPL 3'],
[qr,(?m)^License:.*Artistic(?!-), => 'Artistic'],
[qr,(?m)^License:.*Artistic-2, => 'Artistic 2.0'],
[qr,(?m)^License:.*CC-BY-3.0, => 'CC-BY 3.0'],
[qr,(?m)^License:.*Perl, => 'Artistic'],
[qr,(?m)^License:.*Perl, => 'GPL 1'],
+ [qr,GNU AFFERO GENERAL PUBLIC LICENSE\s+Version 3, => 'AGPL 3'],
[qr,(?i)The Artistic License 2\.0, => 'Artistic 2.0'],
[qr,COMMON DEVELOPMENT AND DISTRIBUTION LICENSE \(CDDL\), => 'CDDL'],
[qr,CONTRAT DE LICENCE DE LOGICIEL LIBRE CeCILL(?!-), => 'CeCILL'],
<chapt> The checklist
-<sect> Version 3.9.2.0
+<sect id="3.9.3.0"> Version 3.9.3.0
<p>
-Released April, 2010.
+Unreleased.
+
+</p><p><taglist>
+<tag>2.4</tag>
+ <item>New archive sections <em>education</em>, <em>introspection</em>,
+ and <em>metapackages</em> added.
+ </item>
+<tag>5.6.8</tag>
+ <item>The <tt>Architecture</tt> field in <file>*.dsc</file> files may
+ now contain the value <tt>any all</tt> for source packages building both
+ architecture-independent and architecture-dependent packages.
+ </item>
+<tag>9.5</tag>
+ <item>Cron job file names must not contain <tt>.</tt> or <tt>+</tt> or
+ they will be ignored by cron. They should replace those characters
+ with <tt>_</tt>. If a package provides multiple cron job files in the
+ same directory, they should each start with the package name (possibly
+ modified as above), <tt>-</tt>, and then some suitable prefix.
+ </item>
+<tag>9.10</tag>
+ <item>Packages using doc-base do not need to call install-docs anymore.
+ </item>
+<tag>11.8</tag>
+ <item>The Policy rules around Motif libraries were just a special case
+ of normal rules for non-free dependencies and were largely obsolete, so
+ they have been removed.
+ </item>
+<tag>12.5</tag>
+ <item><file>debian/copyright</file> is no longer required to list the
+ Debian maintainers involved in the creation of the package (although
+ note that the requirement to list copyright information is unchanged).
+ </item>
+<tag>perl</tag>
+ <item>Packages may declare an interest in the <var>perl-major-upgrade</var>
+ trigger to be notified of major upgrades of perl.
+ </item>
+<tag>virtual</tag>
+ <item><tt>ttf-japanese-{mincho, gothic}</tt> is renamed to
+ <tt>fonts-japanese-{mincho, gothic}</tt>.
+ </item>
+</taglist></p>
+
+<sect id="3.9.2.0"> Version 3.9.2.0
+<p>
+
+Released April, 2011.
</p><p><taglist>
<tag>*</tag>
</item>
</taglist></p>
-<sect> Version 3.9.1.0
+<sect id="3.9.1.0"> Version 3.9.1.0
<p>
Released July, 2010.
</item>
</taglist></p>
-<sect> Version 3.9.0.0
+<sect id="3.9.0.0"> Version 3.9.0.0
<p>
Released June, 2010.
</item>
</taglist></p>
-<sect> Version 3.8.4.0
+<sect id="3.8.4.0"> Version 3.8.4.0
<p>
Release Jan 2010.
</item>
</taglist></p>
-<sect> Version 3.8.3.0
+<sect id="3.8.3.0"> Version 3.8.3.0
<p>
Released Aug 2009.
</item>
</taglist></p>
-<sect> Version 3.8.2.0
+<sect id="3.8.2.0"> Version 3.8.2.0
<p>
Released Jun 2009.
</item>
</taglist></p>
-<sect> Version 3.8.1.0
+<sect id="3.8.1.0"> Version 3.8.1.0
<p>
Released Mar 2009.
</item>
</taglist></p>
-<sect> Version 3.8.0.0
+<sect id="3.8.0.0"> Version 3.8.0.0
<p>
Released Jun 2008.
<item>Underscore (_) is allowed in debconf template names.
</taglist></p>
-<sect> Version 3.7.3.0
+<sect id="3.7.3.0"> Version 3.7.3.0
<p>
Released Dec 2007.
be referenced rather than quoted in debian/copyright.
</taglist></p>
-<sect> Version 3.7.2.2
+<sect id="3.7.2.2"> Version 3.7.2.2
<p>
Released Oct 2006.
should to a must)</item>
</taglist></p>
-<sect> Version 3.7.2.0
+<sect id="3.7.2.0"> Version 3.7.2.0
<p>
Released Apr 2006.
<tag>11.5</tag> <item>Revert the cgi-lib change. </item>
</taglist></p>
-<sect> Version 3.7.1.0
+<sect id="3.7.1.0"> Version 3.7.1.0
<p>
Released Apr 2006.
they do so, they must pre-depend on <tt>x11-common (>= 1:7.0.0)</tt>
</taglist></p>
-<sect> Version 3.7.0.0
+<sect id="3.7.0.0"> Version 3.7.0.0
<p>
Released Apr 2006.
is gone.
</taglist></p>
-<sect> Version 3.6.2.0
+<sect id="3.6.2.0"> Version 3.6.2.0
<p>
Released 2005
</item>
</taglist></p>
-<sect> Version 3.6.1.0
+<sect id="3.6.1.0"> Version 3.6.1.0
<p>
Released Aug 2003.
user prompts are now deprecated.
</taglist></p>
-<sect> Version 3.6.0
+<sect id="3.6.0.0"> Version 3.6.0
<p>
Released Jul 2003.
target.
</taglist></p>
-<sect> Version 3.5.10
+<sect id="3.5.10.0"> Version 3.5.10
<p>
Released May 2003.
Project may add 40 points for ranking in the alternatives
</taglist></p>
-<sect> Version 3.5.9.0
+<sect id="3.5.9.0"> Version 3.5.9.0
<p>
Released Mar 2003.
(rather than <file>/usr/share/doc/package/examples</file>).
</taglist></p>
-<sect> Version 3.5.8.0
+<sect id="3.5.8.0"> Version 3.5.8.0
<p>
Released Nov 2002.
are still a bug.
</taglist></p>
-<sect> Version 3.5.7.0
+<sect id="3.5.7.0"> Version 3.5.7.0
<p>
Released Aug 2002.
rules, please see below
</em></p>
-<sect> Version 3.5.6.0
+<sect id="3.5.6.0"> Version 3.5.6.0
<p>
Released Jul 2001.
there is a new Build-Depend-Indep semantic.
</taglist></p>
-<sect> Version 3.5.5.0
+<sect id="3.5.5.0"> Version 3.5.5.0
<p>
Released May 2001.
</taglist></item>
</taglist></p>
-<sect> Version 3.5.4.0
+<sect id="3.5.4.0"> Version 3.5.4.0
<p> Released Apr 2001.
</p><p><taglist>
</item>
</taglist></p>
-<sect> Version 3.5.3.0
+<sect id="3.5.3.0"> Version 3.5.3.0
<p> Released Apr 2001
</p><p><taglist>
</item>
</taglist></p>
-<sect> Version 3.5.2.0
+<sect id="3.5.2.0"> Version 3.5.2.0
<p> Released Feb 2001.
</item>
</taglist></p>
-<sect> Version 3.5.1.0
+<sect id="3.5.1.0"> Version 3.5.1.0
<p> Released Feb 2001.
</item>
</taglist></p>
-<sect> Version 3.5.0.0
+<sect id="3.5.0.0"> Version 3.5.0.0
<p> Released Jan 2001.
</item>
</taglist></p>
-<sect> Version 3.2.1.1
+<sect id="3.2.1.1"> Version 3.2.1.1
<p> Released Jan 2001.
</item>
</taglist></p>
-<sect> Version 3.2.1.0
+<sect id="3.2.1.0"> Version 3.2.1.0
<p> Released Aug 00.
</item>
</taglist></p>
-<sect> Version 3.2.0.0
+<sect id="3.2.0.0"> Version 3.2.0.0
<p> Released Aug 00.
</item>
</taglist></p>
-<sect> Version 3.1.1.0
+<sect id="3.1.1.0"> Version 3.1.1.0
<p> Released Nov 1999.
</item>
</taglist></p>
-<sect> Version 3.1.0.0
+<sect id="3.1.0.0"> Version 3.1.0.0
<p> Released Oct 1999.
</item>
</taglist></p>
-<sect> Version 3.0.1.0
+<sect id="3.0.1.0"> Version 3.0.1.0
<p> Released Jul 1999.
</item>
</taglist></p>
-<sect> Version 3.0.0.0
+<sect id="3.0.0.0"> Version 3.0.0.0
<p> Released Jun 1999.
Please note that section numbers below this point may not be up to date
</em></p>
-<sect> Version 2.5.0.0
+<sect id="2.5.0.0"> Version 2.5.0.0
<p> Released Oct 1998.
</item>
</list></p>
-<sect> Version 2.4.1.0
+<sect id="2.4.1.0"> Version 2.4.1.0
<p> Released Apr 1998.
</p>
</item>
</list></p>
-<sect> Version 2.4.0.0
+<sect id="2.4.0.0"> Version 2.4.0.0
<p> Released Jan 1998
</item>
</taglist></p>
-<sect> Version 2.3.0.1, 2.3.0.0
+<sect id="2.3.0.0"> Version 2.3.0.1, 2.3.0.0
<p> Released Sep 1997.
<item>MUAs and MTAs have to use liblockfile</item>
</list></p>
-<sect> Version 2.2.0.0
+<sect id="2.2.0.0"> Version 2.2.0.0
<p> Released July 1997.
<item>app-defaults files may not be conffiles</item>
</list></p>
-<sect> Version 2.1.3.2, 2.1.3.1, 2.1.3.0
+<sect id="2.1.3.0"> Version 2.1.3.2, 2.1.3.1, 2.1.3.0
<p> Released Mar 1997.
</item>
</list></p>
-<sect> Version 2.1.2.2, 2.1.2.1, 2.1.2.0
+<sect id="2.1.2.0"> Version 2.1.2.2, 2.1.2.1, 2.1.2.0
<p> Released Nov 1996.
<item>Some changes WRT shared libraries
</list></p>
-<sect> Version 2.1.1.0
+<sect id="2.1.1.0"> Version 2.1.1.0
<p> Released Sep 1996.
<item>Shared libraries must be installed stripped </item>
</list></p>
-<sect> Version 2.1.0.0
+<sect id="2.1.0.0"> Version 2.1.0.0
<p> Released Aug 1996.
Fonts
-----
- ttf-japanese-gothic Gothic-style Japanese font
- ttf-japanese-mincho Mincho-style Japanese font
+ fonts-japanese-gothic Gothic-style Japanese font
+ fonts-japanese-mincho Mincho-style Japanese font
Graphics and MultiMedia
-----------------------
projects / debian / debian-policy.git / commitdiff