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>
-
+
<section id="introduction">
<title>Introduction</title>
<para>
<filename>debian/copyright</filename>.
</para>
</section>
-
+
<section id="rationale">
<title>Rationale</title>
<para>
Lars Wirzenius.
</para>
</section>
-
+
<section id="file-syntax">
<title>File syntax</title>
<para>
There are four kinds values for fields. Each field specifies which kind
is allowed.
</para>
-
+
<section id="single-line">
<title>Single-line values</title>
<para>
that is used.
</para>
</section>
-
+
<section id="white-space-lists">
<title>White space separated lists</title>
<para>
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>
-
+
<section id="line-based-lists">
<title>Line based lists</title>
<para>
line.
</para>
</section>
-
+
<section id="formatted-text">
<title>Text formatted like package long descriptions</title>
<para>
</para>
</section>
</section>
-
+
<section id="paragraphs">
<title>Paragraphs</title>
<para>
license</link> paragraph. This is similar to source and binary package
paragraphs in <filename>debian/control</filename> files.
</para>
-
+
<section id="header-paragraph">
<title>Header paragraph (Once)</title>
<section id="format-header-field">
<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>
-
+
<section id="upstream-name-header-field">
<title><varname>Upstream-Name</varname></title>
<para>
Optional single line: the name upstream uses for the software
</para>
</section>
-
+
<section id="upstream-contact-header-field">
<title><varname>Upstream-Contact</varname></title>
<para>
usually be written as a list of RFC5322 addresses or URIs.
</para>
</section>
-
+
<section id="source-header-field">
<title><varname>Source</varname></title>
<para>
in this field.
</para>
</section>
-
+
<section id="disclaimer-header-field">
<title><varname>Disclaimer</varname></title>
<para>
url="http://www.debian.org/doc/debian-policy/ch-docs#s-copyrightfile">12.5</ulink>)
</para>
</section>
-
+
<section id="comment-header-field">
<title><varname>Comment</varname></title>
<para>
version is not.
</para>
</section>
-
+
<section id="license-header-field">
<title><varname>License</varname></title>
<para>
linkend="files-paragraph">Files paragraph</link> section.
</para>
</section>
-
+
<section id="copyright-header-field">
<title><varname>Copyright</varname></title>
<para>
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>
</section>
</section>
-
+
<section id="files-paragraph">
<title>Files paragraph (Repeatable)</title>
<para>
which applies to all files and lists all applicable copyrights and
licenses.
</para>
-
+
<section id="files-files-field">
<title><varname>Files</varname></title>
<para>
paragraphs.
</para>
</section>
-
+
<section id="copyright-files-field">
<title><varname>Copyright</varname></title>
<para>
notices with the binary package.
</para>
</section>
-
+
<section id="comment-files-field">
<title><varname>Comment</varname></title>
<para>
<varname>Comment</varname></link> field in the header paragraph.
</para>
</section>
-
+
<section id="example-files-paragraph">
<title>Example files paragraphs</title>
<programlisting>Files: *
</para>
</section>
</section>
-
+
<section id="stand-alone-license-paragraph">
<title>Standalone License Paragraph (Optional, Repeatable)</title>
<para>
[LICENSE TEXT]
License: LGPL-2.1
- LICENSE TEXT]</programlisting>
+ [LICENSE TEXT]</programlisting>
</example>
-
+
<example>
<title>recurrent license</title>
<programlisting>Files: src/js/editline/*
<section id="license-specification">
<title>License specification</title>
-
+
<section id="license-short-name">
<title>Short name</title>
<para>
<varname>License</varname> field.
</para>
<para>
- These short names have the specified meanings across all uses of this
+ These short names have the specified meanings across all uses of this
file format, and <emphasis>must not</emphasis> be used to refer to any
other licenses. Parsers may thus rely on these short names referring to
the same licenses wherever they occur, without needing to parse or
</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">
Apache
</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>.
+ Apache license
+ <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>
Artistic
</entry>
<entry>
- Artistic license
+ Artistic license
<ulink url="http://spdx.org/licenses/Artistic-1.0">1.0</ulink>,
<ulink url="http://spdx.org/licenses/Artistic-2.0">2.0</ulink>.
</entry>
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
this exception statement from all source files in the program, then
also delete it here.</programlisting>
</para>
-
+
<section id="public-domain">
<title>Public domain</title>
<para>
</para>
</section>
</section>
-
+
<section id="license-syntax">
<title>Syntax</title>
<para>
version.
.
In addition, as a special exception, the author of this
- program gives permission to link the code of its
+ program gives permission to link the code of its
release with the OpenSSL project's "OpenSSL" library (or
with modified versions of it that use the same license as
the "OpenSSL" library), and distribute the linked
- executables. You must obey the GNU General Public
- License in all respects for all of the code used other
+ executables. You must obey the GNU General Public
+ License in all respects for all of the code used other
than "OpenSSL". If you modify this file, you may extend
this exception to your version of the file, but you are
not obligated to do so. If you do not wish to do so,
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><
projects / debian / debian-policy.git / blobdiff