r201 - /web/deps/dep5.mdwn
plessy at users.alioth.debian.org
plessy at users.alioth.debian.org
Mon Oct 10 04:45:45 UTC 2011
Author: plessy
Date: Mon Oct 10 04:45:44 2011
New Revision: 201
URL: http://svn.debian.org/wsvn/dep/?sc=1&rev=201
Log:
Sync with http://anonscm.debian.org/gitweb/?p=dbnpolicy/policy.git;a=blob;f=copyright-format/copyright-format.xml;hb=b4d036bab75ac794c3500563768d60ad994ae4f1
I will manually sync the dep website with the latest HTML build of the
copyright-format.xml file from the master branch of the Debian Policy's source
repository, until the DEP is marked accepted.
Modified:
web/deps/dep5.mdwn
Modified: web/deps/dep5.mdwn
URL: http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?rev=201&op=diff
==============================================================================
--- web/deps/dep5.mdwn (original)
+++ web/deps/dep5.mdwn Mon Oct 10 04:45:44 2011
@@ -2,11 +2,10 @@
Title: Machine-readable debian/copyright
DEP: 5
- State: CANDIDATE (frozen, about to be ACCEPTED)
- Date: 2011-04-10
- Drivers: Steve Langasek <vorlon at debian.org>,
- Lars Wirzenius <liw at liw.fi>
- URL: http://dep.debian.net/deps/dep5
+ State: CANDIDATE
+ Date: 2011-10-10
+ URL: http://dep.debian.net/deps/dep5 (this page)
+ http://anonscm.debian.org/gitweb/?p=dbnpolicy/policy.git;a=blob;f=copyright-format/copyright-format.xml;hb=b4d036bab75ac794c3500563768d60ad994ae4f1 (the source)
License:
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
@@ -16,689 +15,1368 @@
files within packages, to facilitate automated checking and
reporting of licenses for packages and sets of packages.
-The spec has now been included in the debian-policy package,
-and that is now the official version. This version will no longer
-be change. Only fixes for serious bugs will be accepted at all,
-until transfer to the policy package is final, and after that
-the normal policy process will be used for any further changes.
-
-[[!toc ]]
-
-# Introduction
-
-This is a proposal to make `debian/copyright` machine-interpretable.
-This file is one of the most important files in Debian packaging, yet
-there is currently no standard format defined for it and its contents
-vary tremendously across packages, making it difficult to automatically
-extract licensing information.
-
-This is not a proposal to change the policy in the short term. In
-particular, nothing in this proposal supersedes or modifies any of the
-requirements specified in Debian Policy regarding the appropriate detail or
-granularity to use when documenting copyright and license status in
-`debian/copyright`.
-
-# Rationale
-
-The diversity of free software licenses means that Debian needs to care
-not only about the freeness of a given work, but also its license's
-compatibility with the other parts of Debian it uses.
-
-The arrival of the GPL version 3, its incompatibility with version 2,
-and our inability to spot the software where the incompatibility might
-be problematic is one prominent occurrence of this limitation.
-
-There are earlier precedents, also. One is the GPL/OpenSSL
-incompatibility. Apart from grepping `debian/copyright`, which is
-prone to numerous false positives (packaging under the GPL but software
-under another license) or negatives (GPL software but with an "OpenSSL
-special exception" dual licensing form), there is no reliable way to
-know which software in Debian might be problematic.
-
-And there is more to come. There are issues with shipping GPLv2-only
-software with a CDDL operating system such as Nexenta. The GPL version 3
-solves this issue, but not all GPL software can switch to it and we have
-no way to know how much of Debian should be stripped from such a system.
-
-A user might want to have a way to avoid software with certain licenses
-they have a problem with, even if the licenses are DFSG-free. For
-example, the Affero GPL.
-
-# Acknowledgements
-
-Many people have worked on this specification over the years.
-The following alphabetical list is incomplete,
-please suggest missing people:
-Russ Allbery,
-Ben Finney,
-Sam Hocevar,
-Steve Langasek,
-Charles Plessy,
-Noah Slater,
-Jonas Smedegaard,
-Lars Wirzenius.
-
-# File syntax
-
-The `debian/copyright` file must be machine-interpretable, yet
-human-readable, while communicating all mandated upstream information,
-copyright notices and licensing details.
-
-The syntax of the file is the same as for other Debian control files,
-as specified in section 5.1 of the Debian Policy Manual.
-See
-<http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-controlsyntax>
-for details.
-Extra fields can be added to any paragraph.
-No prefixing is necessary or desired, but please avoid names similar
-to standard ones so that mistakes are easier to catch.
-Future versions of the `debian/copyright`
-specification will attempt to avoid conflicting specifications
-for widely used extra fields.
-
-There are four kinds values for fields. Each field specifies which
-kind is allowed.
-
-* Single-line values.
-* White space separated lists.
-* Line based lists.
-* Text formatted like package long descriptions.
-
-A single-line value means that the whole value of a field must fit on
-a single line. For example, the `Format` field has a single line value
-specifying the version of the machine-readable format that is used.
-
-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 `Files` field has a list of filename patterns.
-
-Another kind of list value has one value per line. For example,
-`Copyright` can list many copyright statements, one per line.
-
-Formatted text fields use the same rules as the long description in
-a package's `Description` field, possibly also using the first
-line as a synopsis, like `Description` uses it for the
-short description.
-See section 5.6.13, "Description", at
-<http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description>
-for details.
-For example, `Disclaimer` has no special first line, whereas
-`License` does.
-
-# Paragraphs
-
-There are three kinds of paragraphs: the first one is called
-the "header paragraph". Every other paragraph is either a "Files"
-paragraph or a stand-alone license paragraph.
-This is similar to source and binary package paragraphs
-in `debian/control` files.
-
-## Header paragraph (Once)
-
- * **`Format`**
- * Required
- * Syntax: single line
- * URI of the format specification, such as:
- * http://svn.debian.org/wsvn/dep/web/deps/dep5.mdwn?op=file&rev=REVISION
-
- * **`Upstream-Name`**
- * Optional
- * Syntax: single line
- * The name upstream uses for the software.
-
- * **`Upstream-Contact`**
- * Optional
- * Syntax: line based list
- * The preferred address(es) to reach
- the upstream project. May be free-form text, but by convention
- will usually be written as a list of RFC5322 addresses or URIs.
-
- * **`Source`**
- * Optional
- * Syntax: formatted text, no synopsis
- * An explanation from where the upstream source came from.
- Typically this would be a URL, but it might be a free-form explanation.
- The [Debian Policy, 12.5](http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile)
- requires this information unless there are no upstream sources,
- which is mainly the case for native Debian packages. If the upstream
- source has been modified to remove non-free parts, that should be
- explained in this field.
-
- * **`Disclaimer`**
- * Optional
- * Syntax: formatted text, no synopsis
- * This field can be
- used in the case of non-free and contrib packages (see [Policy
- 12.5](
- http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile))
-
- * **`Comment`**
- * Optional
- * Syntax: formatted text, no synopsis
- * Description: This field can provide additional information. For
- example, it might quote an e-mail from upstream
- justifying why the license is acceptable to the main archive, or
- an explanation of how this version of the package has been forked
- from a version known to be DFSG-free, even though the current
- upstream version is not.
-
- * **`Copyright`**
- * Optional.
- * Syntax: line based list
- * In the header paragraph (no `Files` specification), this field
- gives the copyright information for the package as a whole, which
- may be different or simplified from a combination of all the
- per-file copyright information. See also `Copyright` below in
- the `Files paragraph` section.
-
- * **`License`**
- * Optional
- * Syntax: formatted text, with synopsis
- * In the header paragraph (no `Files` specification), this field
- gives the license information for the package as a whole, which
- may be different or simplified from a combination of all the
- per-file license information. See also `License` below in
- the `Files paragraph` section.
-
-The `Copyright` and `License` fields in the _header paragraph_ may complement
-but do not replace the _files paragraphs_. They can be used to summarise the
-contributions and redistribution terms for the whole package, for instance when
-a work combines a permissive and a copyleft license, or to document a
-_compilation copyright_ and license. It is possible to use only License
-in the header paragraph, but Copyright alone makes no sense.
-
-Example:
-
- Format: <VERSIONED_FORMAT_URL>
- Upstream-Name: SOFTware
- Upstream-Contact: John Doe <john.doe at example.com>
- Source: http://www.example.com/software/project
-
-## Files paragraph (Repeatable)
-
-The declaration of copyright and license for files is done in one or more
-paragraphs. In the simplest case, a single paragraph can be used which
-applies to all files and lists all applicable copyrights and licenses.
-
- * **`Files`**
- * Required (not in header paragraph).
- * Syntax: white space separated list
- * List of patterns indicating files covered by the license
- and copyright specified in this paragraph. See below for details.
-
- * **`Copyright`**
- * Required
- * Syntax: line based list
- * One or more free-form copyright statement(s), one per line,
- that apply to the files matched by the above pattern.
- If a work has no copyright holder (i.e., it is in the public
- domain), that information should be recorded here.
-
- The Copyright field collects all relevant copyright notices for the
- files of this paragraph. Not all copyright notices may apply to every
- individual file, and years of publication for one copyright holder may
- be gathered together. For example, if file A has:
-
- Copyright 2008 John Smith
- Copyright 2009 Angela Watts
-
- and file B has:
-
- Copyright 2010 Angela Watts
-
- the Copyright field for a stanza covering both file A and file B need
- contain only:
-
- Copyright 2008 John Smith
- Copyright 2009, 2010 Angela Watts
-
- The Copyright field may contain the original copyright statement
- copied exactly (including the word "Copyright"), or it can
- shorten the text, as long as it does not sacrifice information.
- Examples in this specification use both forms.
-
- * **`License`**
- * Licensing terms for the files listed in **`Files`** field for this paragraph
- * Required
- * Syntax: formatted text, with synopsis
- * First line: an abbreviated name for the license, or expression giving
- alternatives (see *Short names* section for a list of standard
- abbreviations). If there are licenses present
- in the package without a standard short name, an arbitrary short
- name may be assigned for these licenses. These arbitrary names
- are only guaranteed to be unique within a single copyright file.
- * Remaining lines: if left blank here, the file **must** include
- a stand-alone **`License`** paragraph matching each license short
- name listed on the first line (see the *Standalone License Paragraph*
- section). Otherwise, this field should either include the full text
- of the license(s) or include a pointer to the license file under
- `/usr/share/common-licenses`. This field should include all text
- needed in order to fulfill both Debian Policy's requirement for
- including a copy of the software's distribution license
- (<a href="http://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile">§12.5</a>),
- and any license requirements to include warranty disclaimers or
- other notices with the binary package.
-
- * **`Comment`**
- * Same as in the header paragraph.
-
-Filename patterns in the `Files` field are specified using a
-simplified shell glob syntax. Patterns are separated by
-white space.
-
-* Only the wildcards `*` and `?` apply; the former matches any number
- of characters (including none), the latter a single character. Both
- match a slash ("`/`") and a leading dot.
-* The backslash ("`\\`") is used to remove the magic from the next
- character; see table below.
-* Patterns match pathnames that start at the root of the source tree.
- Thus, "`Makefile.in`" matches only the file at the root of the tree,
- but "`*/Makefile.in`" matches at any depth.
-
-Backslash escape sequences:
-
- \* match star (asterisk)
- \? match question mark
- \\ match backslash
-
-Any other character following a backslash is an error.
-
-Multiple `Files` paragraphs are allowed. The last paragraph that
-matches a particular file applies to it.
-
-Exclusions are done by having multiple `Files` paragraphs.
-
-Example:
-
- Files: *
- Copyright: 1975-2010 Ulla Upstream
- License: GPL-2+
-
- Files: debian/*
- Copyright: 2010 Daniela Debianizer
- License: GPL-2+
-
- Files: debian/patches/fancy-feature
- Copyright: 2010 Daniela Debianizer
- License: GPL-3+
-
- Files: */*.1
- Copyright: 2010 Manuela Manpager
- License: GPL-2+
-
-In this example, all files are copyright by the upstream and licensed
-under the GPL, version 2 or later, with three exceptions.
-All the Debian packaging files are copyright by the packager,
-and further one specific file providing a new feature is licensed
-differently. Finally, there are some manual pages added to the package,
-written by a third person.
-
-## Standalone License Paragraph (Optional, Repeatable)
-
-Where a set of files are dual (tri, etc) licensed, or when the same license
-occurs multiple times, you can use a single line **`License`** field and
-standalone **`License`** paragraphs to expand the license short names.
-
-Example 1 (tri-licensed files).
-
- Files: src/js/editline/*
- Copyright: 1993, John Doe
- 1993, Joe Average
- License: MPL-1.1 or GPL-2 or LGPL-2.1
-
- License: MPL-1.1
- [LICENSE TEXT]
-
- License: GPL-2
- [LICENSE TEXT]
-
- License: LGPL-2.1
- [LICENSE TEXT]
-
-
-Example 2 (recurrent license).
-
- Files: src/js/editline/*
- Copyright: 1993, John Doe
- 1993, Joe Average
- License: MPL-1.1
-
- Files: src/js/fdlibm/*
- Copyright: 1993, J-Random Corporation
- License: MPL-1.1
-
- License: MPL-1.1
- [LICENSE TEXT]
-
-# License specifications
-
-## Short name
-
-Much of the value of a machine-parseable copyright file lies in being able to
-correlate the licenses of multiple pieces of software. To that end, this
-spec defines standard short names for a number of commonly used licenses,
-which can be used in the first line of a "`License`" field.
-
-These short names have the specified meanings across all uses of this file
-format, and *must not* 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 compare the full license text.
-
-From time to time, licenses may be added to or removed from the list of
-standard short names. Such changes in the list of short names will always
-be accompanied by changes to the recommended `Format` value.
-Implementors who are parsing copyright files should take care not to assume
-anything about the meaning of license short names for unknown
-`Format` versions.
-
-Use of a standard short name does not override the Debian Policy requirement
-to include the full license text in `debian/copyright`, nor any requirements
-in the license of the work regarding reproduction of legal notices. This
-information must still be included in the `License` field, either in a
-stand-alone license paragraph or in the relevant files paragraph.
-
-For licenses which have multiple versions in use, the version number is
-added, using a dash as a separator. If omitted, the lowest version number is
-implied. When the license grant permits using the terms of any later version
-of that license, the short name is finished with a plus sign.
-For SPDX compatibility, trailing "dot-zeroes" are considered to be equal
-to plainer version (e.g., "2.0.0" is considered equal to "2.0" and "2").
-
-Currently, the full text of the licenses is only available in the
-[working version the SPDX license list](http://spdx.org/wiki/working-version-license-list).
-
-
-[[!table data="""
-**keyword** | **meaning**
-`public-domain` | No license required for any purpose; the work is not subject to copyright in any jurisdiction.
-`Apache` | Apache license [1.0](http://spdx.org/licenses/ASL-1.0), [2.0](http://spdx.org/licenses/ASL-2.0).
-`Artistic` | Artistic license [1.0](http://spdx.org/licenses/Artistic-1.0), [2.0](http://spdx.org/licenses/Artistic-2.0).
-`BSD-2-clause` | Berkeley software distribution license, [2-clause version](http://spdx.org/licenses/BSD-2-Clause).
-`BSD-3-clause` | Berkeley software distribution license, [3-clause version](http://spdx.org/licenses/BSD-3-Clause).
-`BSD-4-clause` | Berkeley software distribution license, [4-clause version](http://spdx.org/licenses/BSD-4-Clause).
-`ISC` | [Internet Software Consortium](http://spdx.org/licenses/ISC)'s license, sometimes also known as the OpenBSD License.
-`CC-BY` | Creative Commons Attribution license [1.0](http://spdx.org/licenses/CC-BY-1.0), [2.0](http://spdx.org/licenses/CC-BY-2.0), [2.5](http://spdx.org/licenses/CC-BY-2.5), [3.0](http://spdx.org/licenses/CC-BY-3.0).
-`CC-BY-SA` | Creative Commons Attribution Share Alike license [1.0](http://spdx.org/licenses/CC-BY-SA-1.0), [2.0](http://spdx.org/licenses/CC-BY-SA-2.0), [2.5](http://spdx.org/licenses/CC-BY-SA-2.5), [3.0](http://spdx.org/licenses/CC-BY-SA-3.0).
-`CC-BY-ND` | Creative Commons Attribution No Derivatives license [1.0](http://spdx.org/licenses/CC-BY-ND-1.0), [2.0](http://spdx.org/licenses/CC-BY-ND-2.0), [2.5](http://spdx.org/licenses/CC-BY-ND-2.5), [3.0](http://spdx.org/licenses/CC-BY-ND-3.0).
-`CC-BY-NC` | Creative Commons Attribution Non-Commercial license [1.0](http://spdx.org/licenses/CC-BY-NC-1.0), [2.0](http://spdx.org/licenses/CC-BY-NC-2.0), [2.5](http://spdx.org/licenses/CC-BY-NC-2.5), [3.0](http://spdx.org/licenses/CC-BY-NC-3.0).
-`CC-BY-NC-SA` | Creative Commons Attribution Non-Commercial Share Alike license [1.0](http://spdx.org/licenses/CC-BY-NC-SA-1.0), [2.0](http://spdx.org/licenses/CC-BY-NC-SA-2.0), [2.5](http://spdx.org/licenses/CC-BY-NC-SA-2.5), [3.0](http://spdx.org/licenses/CC-BY-NC-SA-3.0).
-`CC-BY-NC-ND` | Creative Commons Attribution Non-Commercial No Derivatives license [1.0](http://spdx.org/licenses/CC-BY-NC-ND-1.0), [2.0](http://spdx.org/licenses/CC-BY-NC-ND-2.0), [2.5](http://spdx.org/licenses/CC-BY-NC-ND-2.5), [3.0](http://spdx.org/licenses/CC-BY-NC-ND-3.0).
-`CC0` | Creative Commons [Universal waiver](http://creativecommons.org/license/zero/)
-`CDDL` | [Common Development and Distribution License](http://spdx.org/licenses/CDDL).
-`CPL` | [IBM Common Public License](http://spdx.org/licenses/CPL-1.0).
-`EFL` | The Eiffel Forum License [1.0](http://spdx.org/licenses/EPL-1.0).
-`Expat` | The [Expat](http://www.jclark.com/xml/copying.txt) license
-`GPL` | GNU General Public License [1.0](http://spdx.org/licenses/GPL-1.0) [2.0](http://spdx.org/licenses/GPL-2.0) [3.0](http://spdx.org/licenses/GPL-3.0).
-`LGPL` | GNU Lesser General Public License [2.1](http://spdx.org/licenses/LGPL-2.1), [3.0](http://spdx.org/licenses/LGPL-3.0) or GNU Library General Public License [1.0](http://spdx.org/licenses/LGPL-1.0) [2.0](http://spdx.org/licenses/LGPL-2.0).
-`GFDL` | [GNU Free Documentation License](http://spdx.org/licenses/FDL-1.0).
-`GFDL-NIV` | GNU Free Documentation License, with no invariant sections
-`LPPL` | [LaTeX Project Public License](http://www.latex-project.org/lppl/) [1.0](http://spdx.org/licenses/LPPL-1.0), [1.1](http://spdx.org/licenses/LPPL-1.1), [1.2](http://spdx.org/licenses/LPPL-1.2), [1.3c](http://spdx.org/licenses/LPPL-1.3c),
-`MPL` | Mozilla Public License [1.1](http://spdx.org/licenses/MPL-1.1).
-`Perl` | [Perl](http://dev.perl.org/licenses/) license (use "GPL-1+ or Artistic-1" instead)
-`Python-CNRI` | [Python license](http://spdx.org/licenses/Python-CNRI).
-`QPL` | Q Public License [1.0](http://spdx.org/licenses/QPL-1.0).
-`W3C` | [W3C Software License](http://spdx.org/licenses/W3C). For more information, consult the [W3C Intellectual Rights FAQ](http://www.w3.org/Consortium/Legal/IPR-FAQ-20000620).
-`Zlib` | [zlib/libpng license](http://spdx.org/licenses/Zlib).
-`Zope` | Zope Public License [1.0](http://spdx.org/licenses/ZPL-1.0), [2.0](http://spdx.org/licenses/ZPL-2.0), [2.1](http://spdx.org/licenses/ZPL-2.1).
-"""]]
-
-There are [many versions of the MIT
-license](http://en.wikipedia.org/wiki/MIT_License#Various_versions).
-Please use Expat instead, when it matches.
-
-Exceptions and clarifications are signaled in plain text, by appending
-"with '''keywords''' exception" to the short name. This document provides a
-list of keywords that refer to the most frequent exceptions.
-
-The GPL "`Font`" exception refers to the text added to the
-license notice of each file as specified at [How does the GPL apply to
-fonts?](http://www.gnu.org/licenses/gpl-faq.html#FontException). The precise
-text corresponding to this exception is:
-
-> As a special exception, if you create a document which uses this font,
-> and embed this font or unaltered portions of this font into the
-> document, this font does not by itself cause the resulting document to
-> be covered by the GNU General Public License. This exception does not
-> however invalidate any other reasons why the document might be covered
-> by the GNU General Public License. If you modify this font, you may
-> extend this exception to your version of the font, but you are not
-> obligated to do so. If you do not wish to do so, delete this exception
-> statement from your version.
-
-The GPL "`OpenSSL`" exception gives permission to link GPL-licensed
-code with the OpenSSL library, which contains GPL-incompatible clauses.
-For more information, see ["The -OpenSSL License and The
-GPL"](http://www.gnome.org/~markmc/openssl-and-the-gpl.html) by Mark
-McLoughlin and the message ["middleman software license conflicts with
-OpenSSL"](http://lists.debian.org/debian-legal/2004/05/msg00595.html)
-by Mark McLoughlin on the `debian-legal` mailing list. The text corresponding
-to this exception is:
-
-> In addition, as a special exception, the copyright holders give
-> permission to link the code of portions of this program with the
-> OpenSSL library under certain conditions as described in each
-> individual source file, and distribute linked combinations including
-> the two.
-
-> You must obey the GNU General Public License in all respects for all
-> of the code used other than OpenSSL. If you modify file(s) with this
-> exception, you may extend this exception to your version of the
-> file(s), but you are not obligated to do so. If you do not wish to do
-> so, delete this exception statement from your version. If you delete
-> this exception statement from all source files in the program, then
-> also delete it here.
-
-
-### Public domain
-
-The `License` short name `public-domain` does not refer to a set of
-license terms. There are some works which are not subject to copyright
-in any jurisdiction and therefore no license is required for any
-purpose covered by copyright law. This short name is an explicit
-declaration that the associated files are “in the public domainâ€.
-
-Widespread misunderstanding about copyright in general, and the public
-domain in particular, results in the common assertion that a work is
-in the public domain when this is partly or wholly untrue for that
-work. The
-[Wikipedia article on public domain](http://en.wikipedia.org/wiki/Public_domain)
-is a useful reference for this subject.
-
-When the `License` field in a paragraph has the short name
-`public-domain`, the remaining lines of the field **must** explain
-exactly what exemption the corresponding files for that paragraph have
-from default copyright restrictions.
-
-
-## Syntax
-
-License names are case-insensitive, and may not contain spaces.
-
-In case of multi-licensing, the license short names are separated by `or`
-when the user can chose between different licenses, and by `and` when use
-of the work must simultaneously comply with the terms of multiple licenses.
-
-For instance, this is a simple, "GPL version 2 or later" field:
-
- License: GPL-2+
-
-This is a dual-licensed GPL/Artistic work such as Perl:
-
- License: GPL-1+ or Artistic
-
-This is for a file that has both GPL and classic BSD code in it:
-
- License: GPL-2+ and BSD
-
-For the most complex cases, the comma is used to disambiguate the priority of
-`or`s and `and`s: `and` has the priority over `or`, unless preceded by a comma.
-For instance:
-
- `A or B and C` means `A or (B and C)`.
- `A or B, and C` means `(A or B), and C`.
-
-This is for a file that has Perl code and classic BSD code in it:
-
- License: GPL-2+ or Artistic-2.0, and BSD
-
-A GPL-2+ work with the OpenSSL exception is in effect a dual-licensed
-work that can be redistributed either under the GPL-2+, or under the
-GPL-2+ with the OpenSSL exception. It is thus expressed as
-`GPL-2+ with OpenSSL exception`:
-
- License: GPL-2+ with OpenSSL exception
- This program is free software; you can redistribute it
- and/or modify it under the terms of the GNU General Public
- License as published by the Free Software Foundation; either
- version 2 of the License, or (at your option) any later
- version.
- .
- In addition, as a special exception, the author of this
- 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
- 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,
- delete this exception statement from your version.
- .
- This program is distributed in the hope that it will be
- useful, but WITHOUT ANY WARRANTY; without even the implied
- warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
- PURPOSE. See the GNU General Public License for more
- details.
- .
- You should have received a copy of the GNU General Public
- License along with this package; if not, write to the Free
- Software Foundation, Inc., 51 Franklin St, Fifth Floor,
- Boston, MA 02110-1301 USA
- .
- On Debian systems, the full text of the GNU General Public
- License version 2 can be found in the file
- `/usr/share/common-licenses/GPL-2'.
-
-## SPDX
-
-[SPDX](http://spdx.org/) is an attempt to standardize a format
-for communicating the components, licenses and copyrights
-associated with a software package. It and the machine-readable
-`debian/copyright` format attempt to be somewhat compatible.
-However, the two formats have different aims, and so the formats
-are different.
-The [DEP5 wiki page](http://wiki.debian.org/Proposals/CopyrightFormat)
-will be used to track the differences.
-
-
-# Examples
-
-## Simple
-
-A possible `copyright` file for the program 'X Solitaire' distributed in the
-Debian source package `xsol`:
-
- Format: <VERSIONED_FORMAT_URL>
- Upstream-Name: X Solitaire
- Source: ftp://ftp.example.com/pub/games
-
- Files: *
- Copyright: Copyright 1998 John Doe <jdoe at example.com>
- License: GPL-2+
- This program is free software; you can redistribute it
- and/or modify it under the terms of the GNU General Public
- License as published by the Free Software Foundation; either
- version 2 of the License, or (at your option) any later
- version.
- .
- This program is distributed in the hope that it will be
- useful, but WITHOUT ANY WARRANTY; without even the implied
- warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
- PURPOSE. See the GNU General Public License for more
- details.
- .
- You should have received a copy of the GNU General Public
- License along with this package; if not, write to the Free
- Software Foundation, Inc., 51 Franklin St, Fifth Floor,
- Boston, MA 02110-1301 USA
- .
- On Debian systems, the full text of the GNU General Public
- License version 2 can be found in the file
- `/usr/share/common-licenses/GPL-2'.
-
- Files: debian/*
- Copyright: Copyright 1998 Jane Smith <jsmith at example.net>
- License:
- [LICENSE TEXT]
-
-## Complex
-
-A possible `copyright` file for the program 'Planet Venus', distributed in the
-Debian source package `planet-venus`:
-
- Format: <VERSIONED_FORMAT_URL>
- Upstream-Name: Planet Venus
- Upstream-Contact: John Doe <jdoe at example.com>
- Source: http://www.example.com/code/venus
-
- Files: *
- Copyright: 2008, John Doe <jdoe at example.com>
- 2007, Jane Smith <jsmith at example.org>
- 2007, Joe Average <joe at example.org>
- 2007, J. Random User <jr at users.example.com>
- License: PSF-2
- [LICENSE TEXT]
-
- Files: debian/*
- Copyright: 2008, Dan Developer <dan at debian.example.com>
- License:
- 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
- preserved.
-
- Files: debian/patches/theme-diveintomark.patch
- Copyright: 2008, Joe Hacker <hack at example.org>
- License: GPL-2+
- [LICENSE TEXT]
-
- Files: planet/vendor/compat_logging/*
- Copyright: 2002, Mark Smith <msmith at example.org>
- License: MIT
- [LICENSE TEXT]
-
- Files: planet/vendor/httplib2/*
- Copyright: 2006, John Brown <brown at example.org>
- License: MIT2
- Unspecified MIT style license.
-
- Files: planet/vendor/feedparser.py
- Copyright: 2007, Mike Smith <mike at example.org>
- License: PSF-2
- [LICENSE TEXT]
-
- Files: planet/vendor/htmltmpl.py
- Copyright: 2004, Thomas Brown <coder at example.org>
- License: GPL-2+
- This program is free software; you can redistribute it
- and/or modify it under the terms of the GNU General Public
- License as published by the Free Software Foundation; either
- version 2 of the License, or (at your option) any later
- version.
- .
- This program is distributed in the hope that it will be
- useful, but WITHOUT ANY WARRANTY; without even the implied
- warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
- PURPOSE. See the GNU General Public License for more
- details.
- .
- You should have received a copy of the GNU General Public
- License along with this package; if not, write to the Free
- Software Foundation, Inc., 51 Franklin St, Fifth Floor,
- Boston, MA 02110-1301 USA
- .
- On Debian systems, the full text of the GNU General Public
- License version 2 can be found in the file
- `/usr/share/common-licenses/GPL-2'.
+ <div class="ARTICLE">
+ <div class="TITLEPAGE">
+ <h1 class="title"><a name="AEN2" id="AEN2">Machine-readable
+ <tt class="filename">debian/copyright</tt> file.</a></h1>
+
+ <h2 class="subtitle">Version 1.0</h2>
+
+ <div class="legalnotice">
+ <a name="AEN6" id="AEN6"></a>
+
+ <p>Copying and distribution of this file, with or without
+ modification, are permitted in any medium without royalty
+ provided the copyright notice and this notice are
+ preserved.</p>
+ </div>
+
+ <div>
+ <div class="abstract">
+ <a name="AEN8" id="AEN8"></a>
+
+ <p>This specification was drafted as <a href=
+ "http://dep.debian.net/deps/dep5/" target=
+ "_top">DEP-5</a>, to establish a standard,
+ machine-readable format for <tt class=
+ "filename">debian/copyright</tt> files within packages
+ and facilitate automated checking and reporting of
+ licenses for packages and sets of packages.</p>
+ </div>
+ </div>
+ <hr>
+ </div>
+
+ <div class="TOC">
+ <dl>
+ <dt><b>Table of Contents</b></dt>
+
+ <dt><a href="#introduction">Introduction</a></dt>
+
+ <dt><a href="#rationale">Rationale</a></dt>
+
+ <dt><a href="#acknowledgements">Acknowledgements</a></dt>
+
+ <dt><a href="#file-syntax">File syntax</a></dt>
+
+ <dt><a href="#paragraphs">Paragraphs</a></dt>
+
+ <dt><a href="#license-specification">License
+ specification</a></dt>
+
+ <dt><a href="#examples">Examples</a></dt>
+ </dl>
+ </div>
+
+ <div class="section">
+ <h2 class="section"><a name="introduction" id=
+ "introduction">Introduction</a></h2>
+
+ <p>This is a proposal to make <tt class=
+ "filename">debian/copyright</tt> machine-interpretable. This
+ file is one of the most important files in Debian packaging,
+ yet there is currently no standard format defined for it and
+ its contents vary tremendously across packages, making it
+ difficult to automatically extract licensing information.</p>
+
+ <p>This is not a proposal to change the policy in the short
+ term. In particular, nothing in this proposal supersedes or
+ modifies any of the requirements specified in Debian Policy
+ regarding the appropriate detail or granularity to use when
+ documenting copyright and license status in <tt class=
+ "filename">debian/copyright</tt>.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h2 class="section"><a name="rationale" id=
+ "rationale">Rationale</a></h2>
+
+ <p>The diversity of free software licenses means that Debian
+ needs to care not only about the freeness of a given work,
+ but also its license's compatibility with the other parts of
+ Debian it uses.</p>
+
+ <p>The arrival of the GPL version 3, its incompatibility with
+ version 2, and our inability to spot the software where the
+ incompatibility might be problematic is one prominent
+ occurrence of this limitation.</p>
+
+ <p>There are earlier precedents, also. One is the GPL/OpenSSL
+ incompatibility. Apart from grepping <tt class=
+ "filename">debian/copyright</tt>, which is prone to numerous
+ false positives (packaging under the GPL but software under
+ another license) or negatives (GPL software but with an
+ <span class="QUOTE">"OpenSSL special exception"</span> dual
+ licensing form), there is no reliable way to know which
+ software in Debian might be problematic.</p>
+
+ <p>And there is more to come. There are issues with shipping
+ GPLv2-only software with a CDDL operating system such as
+ Nexenta. The GPL version 3 solves this issue, but not all GPL
+ software can switch to it and we have no way to know how much
+ of Debian should be stripped from such a system.</p>
+
+ <p>A user might want to have a way to avoid software with
+ certain licenses they have a problem with, even if the
+ licenses are DFSG-free. For example, the Affero GPL.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h2 class="section"><a name="acknowledgements" id=
+ "acknowledgements">Acknowledgements</a></h2>
+
+ <p>Many people have worked on this specification over the
+ years. The following alphabetical list is incomplete, please
+ suggest missing people: Russ Allbery, Ben Finney, Sam
+ Hocevar, Steve Langasek, Charles Plessy, Noah Slater, Jonas
+ Smedegaard, Lars Wirzenius.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h2 class="section"><a name="file-syntax" id=
+ "file-syntax">File syntax</a></h2>
+
+ <p>The <tt class="filename">debian/copyright</tt> file must
+ be machine-interpretable, yet human-readable, while
+ communicating all mandated upstream information, copyright
+ notices and licensing details.</p>
+
+ <p>The syntax of the file is the same as for other Debian
+ control files, as specified in the Debian Policy Manual. See
+ its <a href=
+ "http://www.debian.org/doc/debian-policy/ch-controlfields#s-controlsyntax"
+ target="_top">section 5.1</a> for details. Extra fields can
+ be added to any paragraph. No prefixing is necessary or
+ desired, but please avoid names similar to standard ones so
+ that mistakes are easier to catch. Future versions of the
+ <tt class="filename">debian/copyright</tt> specification will
+ attempt to avoid conflicting specifications for widely used
+ extra fields.</p>
+
+ <p>There are four kinds values for fields. Each field
+ specifies which kind is allowed.</p>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="single-line" id=
+ "single-line">Single-line values</a></h3>
+
+ <p>A single-line value means that the whole value of a
+ field must fit on a single line. For example, the
+ <code class="varname">Format</code> field has a single line
+ value specifying the version of the machine-readable format
+ that is used.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="white-space-lists" id=
+ "white-space-lists">White space separated lists</a></h3>
+
+ <p>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 <code class=
+ "varname">Files</code> field has a list of filename
+ patterns.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="line-based-lists" id=
+ "line-based-lists">Line based lists</a></h3>
+
+ <p>Another kind of list value has one value per line. For
+ example, <code class="varname">Copyright</code> can list
+ many copyright statements, one per line.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="formatted-text" id=
+ "formatted-text">Text formatted like package long
+ descriptions</a></h3>
+
+ <p>Formatted text fields use the same rules as the long
+ description in a package's <code class=
+ "varname">Description</code> field, possibly also using the
+ first line as a synopsis, like <code class=
+ "varname">Description</code> uses it for the short
+ description. See Debian Policy's section 5.6.13, <a href=
+ "http://www.debian.org/doc/debian-policy/ch-controlfields#s-f-Description"
+ target="_top"><span class="QUOTE">"Description"</span></a>,
+ for details. For example, <code class=
+ "varname">Disclaimer</code> has no special first line,
+ whereas <code class="varname">License</code> does.</p>
+ </div>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h2 class="section"><a name="paragraphs" id=
+ "paragraphs">Paragraphs</a></h2>
+
+ <p>There are three kinds of paragraphs: the first one is
+ called the <a href="#header-paragraph">header paragraph</a>.
+ Every other paragraph is either a <a href=
+ "#files-paragraph">Files</a> paragraph or a <a href=
+ "#stand-alone-license-paragraph">stand-alone license</a>
+ paragraph. This is similar to source and binary package
+ paragraphs in <tt class="filename">debian/control</tt>
+ files.</p>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="header-paragraph" id=
+ "header-paragraph">Header paragraph (Once)</a></h3>
+
+ <div class="section">
+ <h4 class="section"><a name="format-header-field" id=
+ "format-header-field"><code class=
+ "varname">Format</code></a></h4>
+
+ <p>Required single line: URI of the format specification,
+ such as: <tt class=
+ "literal">http://www.debian.org/doc/copyright-format/1.0</tt></p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="upstream-name-header-field"
+ id="upstream-name-header-field"><code class=
+ "varname">Upstream-Name</code></a></h4>
+
+ <p>Optional single line: the name upstream uses for the
+ software</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name=
+ "upstream-contact-header-field" id=
+ "upstream-contact-header-field"><code class=
+ "varname">Upstream-Contact</code></a></h4>
+
+ <p>Optional line based list: the preferred address(es) to
+ reach the upstream project. May be free-form text, but by
+ convention will usually be written as a list of RFC5322
+ addresses or URIs.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="source-header-field" id=
+ "source-header-field"><code class=
+ "varname">Source</code></a></h4>
+
+ <p>Optional formatted text, no synopsis: an explanation
+ from where the upstream source came from. Typically this
+ would be a URL, but it might be a free-form explanation.
+ The Debian Policy section <a href=
+ "http://www.debian.org/doc/debian-policy/ch-docs#s-copyrightfile"
+ target="_top">12.5</a> requires this information unless
+ there are no upstream sources, which is mainly the case
+ for native Debian packages. If the upstream source has
+ been modified to remove non-free parts, that should be
+ explained in this field.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="disclaimer-header-field" id=
+ "disclaimer-header-field"><code class=
+ "varname">Disclaimer</code></a></h4>
+
+ <p>Optional formatted text, no synopsis: this field can
+ be used in the case of non-free and contrib packages (see
+ <a href=
+ "http://www.debian.org/doc/debian-policy/ch-docs#s-copyrightfile"
+ target="_top">12.5</a>)</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="comment-header-field" id=
+ "comment-header-field"><code class=
+ "varname">Comment</code></a></h4>
+
+ <p>Optional formatted text, no synopsis: this field can
+ provide additional information. For example, it might
+ quote an e-mail from upstream justifying why the license
+ is acceptable to the main archive, or an explanation of
+ how this version of the package has been forked from a
+ version known to be DFSG-free, even though the current
+ upstream version is not.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="license-header-field" id=
+ "license-header-field"><code class=
+ "varname">License</code></a></h4>
+
+ <p>Optional formatted text, with synopsis: in the header
+ paragraph (no <code class="varname">Files</code>
+ specification), this field gives the license information
+ for the package as a whole, which may be different or
+ simplified from a combination of all the per-file license
+ information. <code class="varname">License</code> below
+ in the <a href="#files-paragraph">Files paragraph</a>
+ section.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="copyright-header-field" id=
+ "copyright-header-field"><code class=
+ "varname">Copyright</code></a></h4>
+
+ <p>Optional line based list: in the header paragraph (no
+ <code class="varname">Files</code> specification), this
+ field gives the copyright information for the package as
+ a whole, which may be different or simplified from a
+ combination of all the per-file copyright information.
+ See also <code class="varname">Copyright</code> below in
+ the <a href="#files-paragraph">Files paragraph</a>
+ section.</p>
+
+ <p>The <code class="varname">Copyright</code> and
+ <code class="varname">License</code> fields in the
+ <span class="emphasis"><i class="emphasis">header
+ paragraph</i></span> may complement but do not replace
+ the <span class="emphasis"><i class="emphasis">files
+ paragraphs</i></span>. They can be used to summarise the
+ contributions and redistribution terms for the whole
+ package, for instance when a work combines a permissive
+ and a copyleft license, or to document a <span class=
+ "emphasis"><i class="emphasis">compilation
+ copyright</i></span> and license. It is possible to use
+ only <code class="varname">License</code> in the header
+ paragraph, but <code class="varname">Copyright</code>
+ alone makes no sense.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="example-header-paragraph"
+ id="example-header-paragraph">Example header
+ paragraph</a></h4>
+ <pre class="programlisting">
+Format: <VERSIONED_FORMAT_URL>
+Upstream-Name: SOFTware
+Upstream-Contact: John Doe <john.doe at example.com>
+Source: http://www.example.com/software/project
+</pre>
+ </div>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="files-paragraph" id=
+ "files-paragraph">Files paragraph (Repeatable)</a></h3>
+
+ <p>The declaration of copyright and license for files is
+ done in one or more paragraphs. In the simplest case, a
+ single paragraph can be used which applies to all files and
+ lists all applicable copyrights and licenses.</p>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="files-files-field" id=
+ "files-files-field"><code class=
+ "varname">Files</code></a></h4>
+
+ <p>Required white space separated list: list of patterns
+ indicating files covered by the license and copyright
+ specified in this paragraph.</p>
+
+ <p>Filename patterns in the <code class=
+ "varname">Files</code> field are specified using a
+ simplified shell glob syntax. Patterns are separated by
+ white space.</p>
+
+ <ul>
+ <li>
+ <p>Only the wildcards <tt class="literal">*</tt> and
+ <tt class="literal">?</tt> apply; the former matches
+ any number of characters (including none), the latter
+ a single character. Both match a slash (<tt class=
+ "literal">/</tt>) and a leading dot.</p>
+ </li>
+
+ <li>
+ <p>Patterns match pathnames that start at the root of
+ the source tree. Thus, <span class=
+ "QUOTE">"<tt class="filename">Makefile.in</tt>"</span>
+ matches only the file at the root of the tree, but
+ <span class="QUOTE">"<tt class=
+ "filename">*/Makefile.in</tt>"</span> matches at any
+ depth.</p>
+ </li>
+
+ <li>
+ <p>The backslash (<tt class="literal">\</tt>) is used
+ to remove the magic from the next character; see
+ table below.</p>
+ </li>
+ </ul>
+
+ <div class="informaltable">
+ <a name="AEN144" id="AEN144"></a>
+
+ <table border="1" class="CALSTABLE">
+ <col>
+ <col>
+
+ <thead>
+ <tr>
+ <th>Escape sequence</th>
+
+ <th>Matches</th>
+ </tr>
+ </thead>
+
+ <tbody>
+ <tr>
+ <td><tt class="literal">\*</tt></td>
+
+ <td>star (asterisk)</td>
+ </tr>
+
+ <tr>
+ <td><tt class="literal">\?</tt></td>
+
+ <td>question mark</td>
+ </tr>
+
+ <tr>
+ <td><tt class="literal">\\</tt></td>
+
+ <td>backslash</td>
+ </tr>
+ </tbody>
+ </table>
+ </div>Any other character following a backslash is an
+ error.
+
+ <p>Multiple <code class="varname">Files</code> paragraphs
+ are allowed. The last paragraph that matches a particular
+ file applies to it.</p>
+
+ <p>Exclusions are done by having multiple <code class=
+ "varname">Files</code> paragraphs.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="copyright-files-field" id=
+ "copyright-files-field"><code class=
+ "varname">Copyright</code></a></h4>
+
+ <p>Required line based list: one or more free-form
+ copyright statement(s), one per line, that apply to the
+ files matched by the above pattern. If a work has no
+ copyright holder (i.e., it is in the public domain), that
+ information should be recorded here.</p>
+
+ <p>The <code class="varname">Copyright</code> field
+ collects all relevant copyright notices for the files of
+ this paragraph. Not all copyright notices may apply to
+ every individual file, and years of publication for one
+ copyright holder may be gathered together. For example,
+ if file A has:</p>
+ <pre class="programlisting">
+Copyright 2008 John Smith
+Copyright 2009 Angela Watts
+</pre>and file B has:
+ <pre class="programlisting">
+Copyright 2010 Angela Watts
+</pre>the <code class="varname">Copyright</code> field for a stanza
+covering both file A and file B need contain only:
+ <pre class="programlisting">
+Copyright 2008 John Smith
+Copyright 2009, 2010 Angela Watts
+</pre>
+
+ <p>The <code class="varname">Copyright</code> field may
+ contain the original copyright statement copied exactly
+ (including the word <span class=
+ "QUOTE">"Copyright"</span>), or it can shorten the text,
+ as long as it does not sacrifice information. Examples in
+ this specification use both forms.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="license-files-field" id=
+ "license-files-field"><code class=
+ "varname">License</code></a></h4>
+
+ <p>Required formatted text, with synopsis: licensing
+ terms for the files listed in <code class=
+ "varname">Files</code> field for this paragraph.</p>
+
+ <p>First line: an abbreviated name for the license, or
+ expression giving alternatives (see <a href=
+ "#license-short-name">Short names</a> section for a list
+ of standard abbreviations). If there are licenses present
+ in the package without a standard short name, an
+ arbitrary short name may be assigned for these licenses.
+ These arbitrary names are only guaranteed to be unique
+ within a single copyright file.</p>
+
+ <p>Remaining lines: if left blank here, the file
+ <span class="emphasis"><i class=
+ "emphasis">must</i></span> include a stand-alone
+ <code class="varname">License</code> paragraph matching
+ each license short name listed on the first line (see the
+ <a href="#stand-alone-license-paragraph">Standalone
+ License Paragraph</a> section). Otherwise, this field
+ should either include the full text of the license(s) or
+ include a pointer to the license file under <tt class=
+ "filename">/usr/share/common-licenses</tt>. This field
+ should include all text needed in order to fulfill both
+ Debian Policy's requirement for including a copy of the
+ software's distribution license (<a href=
+ "http://www.debian.org/doc/debian-policy/ch-docs#s-copyrightfile"
+ target="_top">12.5</a>), and any license requirements to
+ include warranty disclaimers or other notices with the
+ binary package.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="comment-files-field" id=
+ "comment-files-field"><code class=
+ "varname">Comment</code></a></h4>
+
+ <p>Same as the <a href="#comment-header-field">
+ <code class="varname">Comment</code></a> field in the
+ header paragraph.</p>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="example-files-paragraph" id=
+ "example-files-paragraph">Example files
+ paragraphs</a></h4>
+ <pre class="programlisting">
+Files: *
+Copyright: 1975-2010 Ulla Upstream
+License: GPL-2+
+
+Files: debian/*
+Copyright: 2010 Daniela Debianizer
+License: GPL-2+
+
+Files: debian/patches/fancy-feature
+Copyright: 2010 Daniela Debianizer
+License: GPL-3+
+
+Files: */*.1
+Copyright: 2010 Manuela Manpager
+License: GPL-2+
+</pre>
+
+ <p>In this example, all files are copyright by the
+ upstream and licensed under the GPL, version 2 or later,
+ with three exceptions. All the Debian packaging files are
+ copyright by the packager, and further one specific file
+ providing a new feature is licensed differently. Finally,
+ there are some manual pages added to the package, written
+ by a third person.</p>
+ </div>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="stand-alone-license-paragraph"
+ id="stand-alone-license-paragraph">Standalone License
+ Paragraph (Optional, Repeatable)</a></h3>
+
+ <p>Where a set of files are dual (tri, etc) licensed, or
+ when the same license occurs multiple times, you can use a
+ single line <code class="varname">License</code> field and
+ standalone <code class="varname">License</code> paragraphs
+ to expand the license short names.</p>
+
+ <div class="example">
+ <a name="AEN208" id="AEN208"></a>
+
+ <p><b>Example 1. tri-licensed files</b></p>
+ <pre class="programlisting">
+Files: src/js/editline/*
+Copyright: 1993, John Doe
+ 1993, Joe Average
+License: MPL-1.1 or GPL-2 or LGPL-2.1
+
+License: MPL-1.1
+ [LICENSE TEXT]
+
+License: GPL-2
+ [LICENSE TEXT]
+
+License: LGPL-2.1
+ LICENSE TEXT]
+</pre>
+ </div>
+
+ <div class="example">
+ <a name="AEN211" id="AEN211"></a>
+
+ <p><b>Example 2. recurrent license</b></p>
+ <pre class="programlisting">
+Files: src/js/editline/*
+Copyright: 1993, John Doe
+ 1993, Joe Average
+License: MPL-1.1
+
+Files: src/js/fdlibm/*
+Copyright: 1993, J-Random Corporation
+License: MPL-1.1
+
+License: MPL-1.1
+ [LICENSE TEXT]
+</pre>
+ </div>
+ </div>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h2 class="section"><a name="license-specification" id=
+ "license-specification">License specification</a></h2>
+
+ <div class="section">
+ <h3 class="section"><a name="license-short-name" id=
+ "license-short-name">Short name</a></h3>
+
+ <p>Much of the value of a machine-parseable copyright file
+ lies in being able to correlate the licenses of multiple
+ pieces of software. To that end, this spec defines standard
+ short names for a number of commonly used licenses, which
+ can be used in the first line of a <code class=
+ "varname">License</code> field.</p>
+
+ <p>These short names have the specified meanings across all
+ uses of this file format, and <span class=
+ "emphasis"><i class="emphasis">must not</i></span> 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 compare the full
+ license text.</p>
+
+ <p>From time to time, licenses may be added to or removed
+ from the list of standard short names. Such changes in the
+ list of short names will always be accompanied by changes
+ to the recommended <code class="varname">Format</code>
+ value. Implementers who are parsing copyright files should
+ take care not to assume anything about the meaning of
+ license short names for unknown <code class=
+ "varname">Format</code> versions.</p>
+
+ <p>Use of a standard short name does not override the
+ Debian Policy requirement to include the full license text
+ in <tt class="filename">debian/copyright</tt>, nor any
+ requirements in the license of the work regarding
+ reproduction of legal notices. This information must still
+ be included in the <code class="varname">License</code>
+ field, either in a stand-alone license paragraph or in the
+ relevant files paragraph.</p>
+
+ <p>For licenses which have multiple versions in use, the
+ version number is added, using a dash as a separator. If
+ omitted, the lowest version number is implied. When the
+ license grant permits using the terms of any later version
+ of that license, the short name is finished with a plus
+ sign. For <a href="#spdx">SPDX</a> compatibility, trailing
+ <span class="emphasis"><i class=
+ "emphasis">dot-zeroes</i></span> are considered to be equal
+ to plainer version (e.g., <span class=
+ "QUOTE">"2.0.0"</span> is considered equal to <span class=
+ "QUOTE">"2.0"</span> and <span class=
+ "QUOTE">"2"</span>).</p>
+
+ <p>Currently, the full text of the licenses is only
+ available in the <a href="http://spdx.org/licenses" target=
+ "_top">SPDX Open Source License Registry</a>.</p>
+
+ <div class="informaltable">
+ <a name="AEN236" id="AEN236"></a>
+
+ <table border="1" class="CALSTABLE">
+ <col>
+ <col>
+
+ <thead>
+ <tr>
+ <th>Keyword</th>
+
+ <th>Meaning</th>
+ </tr>
+ </thead>
+
+ <tbody>
+ <tr>
+ <td>public-domain</td>
+
+ <td>No license required for any purpose; the work
+ is not subject to copyright in any
+ jurisdiction.</td>
+ </tr>
+
+ <tr>
+ <td>Apache</td>
+
+ <td>Apache license <a href=
+ "http://spdx.org/licenses/ASL-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/ASL-2.0" target=
+ "_top">2.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>Artistic</td>
+
+ <td>Artistic license <a href=
+ "http://spdx.org/licenses/Artistic-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/Artistic-2.0" target=
+ "_top">2.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>BSD-2-clause</td>
+
+ <td>Berkeley software distribution license,
+ <a href="http://spdx.org/licenses/BSD-2-Clause"
+ target="_top">2-clause version</a>.</td>
+ </tr>
+
+ <tr>
+ <td>BSD-3-clause</td>
+
+ <td>Berkeley software distribution license,
+ <a href="http://spdx.org/licenses/BSD-3-Clause"
+ target="_top">3-clause version</a>.</td>
+ </tr>
+
+ <tr>
+ <td>BSD-4-clause</td>
+
+ <td>Berkeley software distribution license,
+ <a href="http://spdx.org/licenses/BSD-4-Clause"
+ target="_top">4-clause version</a>.</td>
+ </tr>
+
+ <tr>
+ <td>ISC</td>
+
+ <td><a href="http://spdx.org/licenses/ISC" target=
+ "_top">Internet Software Consortium</a>, sometimes
+ also known as the OpenBSD License.</td>
+ </tr>
+
+ <tr>
+ <td>CC-BY</td>
+
+ <td>Creative Commons Attribution license <a href=
+ "http://spdx.org/licenses/CC-BY-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-2.5" target=
+ "_top">2.5</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-3.0" target=
+ "_top">3.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CC-BY-SA</td>
+
+ <td>Creative Commons Attribution Share Alike
+ license <a href=
+ "http://spdx.org/licenses/CC-BY-SA-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-SA-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-SA-2.5" target=
+ "_top">2.5</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-SA-3.0" target=
+ "_top">3.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CC-BY-ND</td>
+
+ <td>Creative Commons Attribution No Derivatives
+ license <a href=
+ "http://spdx.org/licenses/CC-BY-ND-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-ND-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-ND-2.5" target=
+ "_top">2.5</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-ND-3.0" target=
+ "_top">3.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CC-BY-NC</td>
+
+ <td>Creative Commons Attribution Non-Commercial
+ license <a href=
+ "http://spdx.org/licenses/CC-BY-NC-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-2.5" target=
+ "_top">2.5</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-3.0" target=
+ "_top">3.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CC-BY-NC-SA</td>
+
+ <td>Creative Commons Attribution Non-Commercial
+ Share Alike license <a href=
+ "http://spdx.org/licenses/CC-BY-NC-SA-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-SA-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-SA-2.5" target=
+ "_top">2.5</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-SA-3.0" target=
+ "_top">3.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CC-BY-NC-ND</td>
+
+ <td>Creative Commons Attribution Non-Commercial No
+ Derivatives license <a href=
+ "http://spdx.org/licenses/CC-BY-NC-ND-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-ND-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-ND-2.5" target=
+ "_top">2.5</a>, <a href=
+ "http://spdx.org/licenses/CC-BY-NC-ND-3.0" target=
+ "_top">3.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CC0</td>
+
+ <td>Creative Commons <a href=
+ "http://creativecommons.org/license/zero/" target=
+ "_top">Universal waiver</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CDDL</td>
+
+ <td><a href="http://spdx.org/licenses/CDDL" target=
+ "_top">Common Development and Distribution
+ License</a>.</td>
+ </tr>
+
+ <tr>
+ <td>CPL</td>
+
+ <td><a href="http://spdx.org/licenses/CPL-1.0"
+ target="_top">IBM Common Public License</a>.</td>
+ </tr>
+
+ <tr>
+ <td>EFL</td>
+
+ <td>The Eiffel Forum License <a href=
+ "http://spdx.org/licenses/EFL-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/EFL-2.0" target=
+ "_top">2.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>Expat</td>
+
+ <td>The <a href=
+ "http://www.jclark.com/xml/copying.txt" target=
+ "_top">Expat</a> license.</td>
+ </tr>
+
+ <tr>
+ <td>GPL</td>
+
+ <td>GNU General Public License <a href=
+ "http://spdx.org/licenses/GPL-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/GPL-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/GPL-3.0" target=
+ "_top">3.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>LGPL</td>
+
+ <td>GNU Lesser General Public License <a href=
+ "http://spdx.org/licenses/LGPL-2.1" target=
+ "_top">2.1</a>, <a href=
+ "http://spdx.org/licenses/LGPL-3.0" target=
+ "_top">3.0</a>, or GNU Library General Public
+ License <a href="http://spdx.org/licenses/LGPL-1.0"
+ target="_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/LGPL-2.0" target=
+ "_top">2.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>GFDL</td>
+
+ <td><a href="http://spdx.org/licenses/FDL-1.0"
+ target="_top">GNU Free Documentation
+ License</a>.</td>
+ </tr>
+
+ <tr>
+ <td>GFDL-NIV</td>
+
+ <td>GNU Free Documentation License, with no
+ invariant sections.</td>
+ </tr>
+
+ <tr>
+ <td>LPPL</td>
+
+ <td><a href="http://www.latex-project.org/lppl/"
+ target="_top">LaTeX Project Public License</a>
+ <a href="http://spdx.org/licenses/LPPL-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/LPPL-1.1" target=
+ "_top">1.1</a>, <a href=
+ "http://spdx.org/licenses/LPPL-1.2" target=
+ "_top">1.2</a>, <a href=
+ "http://spdx.org/licenses/LPPL-1.3c" target=
+ "_top">1.3c</a>.</td>
+ </tr>
+
+ <tr>
+ <td>MPL</td>
+
+ <td>Mozilla Public License <a href=
+ "http://spdx.org/licenses/MPL-1.1" target=
+ "_top">1.1</a>.</td>
+ </tr>
+
+ <tr>
+ <td>Perl</td>
+
+ <td><a href="http://dev.perl.org/licenses/" target=
+ "_top">Perl</a> license (use <span class=
+ "QUOTE">"<tt class="literal">GPL-1+ or
+ Artistic-1</tt>"</span> instead).</td>
+ </tr>
+
+ <tr>
+ <td>Python-CNRI</td>
+
+ <td><a href="http://spdx.org/licenses/Python-CNRI"
+ target="_top">Python license</a>.</td>
+ </tr>
+
+ <tr>
+ <td>QPL</td>
+
+ <td>Q Public License <a href=
+ "http://spdx.org/licenses/QPL-1.0" target=
+ "_top">1.0</a>.</td>
+ </tr>
+
+ <tr>
+ <td>W3C</td>
+
+ <td><a href="http://spdx.org/licenses/W3C" target=
+ "_top">W3C Software License</a> For more
+ information, consult the <a href=
+ "http://www.w3.org/Consortium/Legal/IPR-FAQ-20000620"
+ target="_top">W3C Intellectual Rights FAQ</a>.</td>
+ </tr>
+
+ <tr>
+ <td>Zlib</td>
+
+ <td><a href="http://spdx.org/licenses/Zlib" target=
+ "_top">zlib/libpng license</a>.</td>
+ </tr>
+
+ <tr>
+ <td>Zope</td>
+
+ <td>Zope Public License <a href=
+ "http://spdx.org/licenses/ZPL-1.0" target=
+ "_top">1.0</a>, <a href=
+ "http://spdx.org/licenses/ZPL-2.0" target=
+ "_top">2.0</a>, <a href=
+ "http://spdx.org/licenses/ZPL-2.1" target=
+ "_top">2.1</a>.</td>
+ </tr>
+ </tbody>
+ </table>
+ </div>
+
+ <p>There are <a href=
+ "http://en.wikipedia.org/wiki/MIT_License#Various_versions"
+ target="_top">many versions of the MIT license</a>. Please
+ use Expat instead, when it matches.</p>
+
+ <p>Exceptions and clarifications are signaled in plain
+ text, by appending <tt class="literal">with <code class=
+ "varname"><tt class=
+ "replaceable"><i>keywords</i></tt></code> exception</tt> to
+ the short name. This document provides a list of keywords
+ that refer to the most frequent exceptions.</p>
+
+ <p>The GPL <tt class="literal">Font</tt> exception refers
+ to the text added to the license notice of each file as
+ specified at <a href=
+ "http://www.gnu.org/licenses/gpl-faq#FontException" target=
+ "_top">How does the GPL apply to fonts</a>. The precise
+ text corresponding to this exception is:</p>
+ <pre class="programlisting">
+As a special exception, if you create a document which uses this font,
+and embed this font or unaltered portions of this font into the
+document, this font does not by itself cause the resulting document to
+be covered by the GNU General Public License. This exception does not
+however invalidate any other reasons why the document might be covered
+by the GNU General Public License. If you modify this font, you may
+extend this exception to your version of the font, but you are not
+obligated to do so. If you do not wish to do so, delete this exception
+statement from your version.
+</pre>
+
+ <p>The GPL <tt class="literal">OpenSSL</tt> exception gives
+ permission to link GPL-licensed code with the OpenSSL
+ library, which contains GPL-incompatible clauses. For more
+ information, see <a href=
+ "http://www.gnome.org/~markmc/openssl-and-the-gpl" target=
+ "_top">The -OpenSSL License and The GPL</a> by Mark
+ McLoughlin and the message <a href=
+ "http://lists.debian.org/debian-legal/2004/05/msg00595.html"
+ target="_top">middleman software license conflicts with
+ OpenSSL</a> by Mark McLoughlin on the <span class=
+ "emphasis"><i class="emphasis">debian-legal</i></span>
+ mailing list. The text corresponding to this exception
+ is:</p>
+ <pre class="programlisting">
+In addition, as a special exception, the copyright holders give
+permission to link the code of portions of this program with the
+OpenSSL library under certain conditions as described in each
+individual source file, and distribute linked combinations including
+the two.
+
+You must obey the GNU General Public License in all respects for all
+of the code used other than OpenSSL. If you modify file(s) with this
+exception, you may extend this exception to your version of the
+file(s), but you are not obligated to do so. If you do not wish to do
+so, delete this exception statement from your version. If you delete
+this exception statement from all source files in the program, then
+also delete it here.
+</pre>
+
+ <div class="section">
+ <hr>
+
+ <h4 class="section"><a name="public-domain" id=
+ "public-domain">Public domain</a></h4>
+
+ <p>The <code class="varname">License</code> short name
+ <tt class="literal">public-domain</tt> does not refer to
+ a set of license terms. There are some works which are
+ not subject to copyright in any jurisdiction and
+ therefore no license is required for any purpose covered
+ by copyright law. This short name is an explicit
+ declaration that the associated files are <span class=
+ "QUOTE">"in the public domain"</span>.</p>
+
+ <p>Widespread misunderstanding about copyright in
+ general, and the public domain in particular, results in
+ the common assertion that a work is in the public domain
+ when this is partly or wholly untrue for that work. The
+ <a href="http://en.wikipedia.org/wiki/Public_domain"
+ target="_top">Wikipedia article on public domain</a> is a
+ useful reference for this subject.</p>
+
+ <p>When the <code class="varname">License</code> field in
+ a paragraph has the short name <tt class=
+ "literal">public-domain</tt>, the remaining lines of the
+ field <span class="emphasis"><i class=
+ "emphasis">must</i></span> explain exactly what exemption
+ the corresponding files for that paragraph have from
+ default copyright restrictions.</p>
+ </div>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="license-syntax" id=
+ "license-syntax">Syntax</a></h3>
+
+ <p>License names are case-insensitive, and may not contain
+ spaces.</p>
+
+ <p>In case of multi-licensing, the license short names are
+ separated by <tt class="literal">or</tt> when the user can
+ chose between different licenses, and by <tt class=
+ "literal">and</tt> when use of the work must simultaneously
+ comply with the terms of multiple licenses.</p>
+
+ <p>For instance, this is a simple, <span class="QUOTE">"GPL
+ version 2 or later"</span> field:</p>
+ <pre class="programlisting">
+License: GPL-2+
+</pre>This is a dual-licensed GPL/Artistic work such as Perl:
+ <pre class="programlisting">
+License: GPL-1+ or Artistic
+</pre>This is for a file that has both GPL and classic BSD code in
+it:
+ <pre class="programlisting">
+License: GPL-2+ and BSD
+</pre>For the most complex cases, the comma is used to disambiguate
+the priority of <tt class="literal">or</tt>s and <tt class=
+"literal">and</tt>s <tt class="literal">and</tt> has the priority
+over <tt class="literal">or</tt>, unless preceded by a comma. For
+instance:
+
+ <p><tt class="literal">A or B and C</tt> means <tt class=
+ "literal">A or (B and C)</tt>.</p>
+
+ <p><tt class="literal">A or B, and C</tt> means <tt class=
+ "literal">(A or B), and C</tt>.</p>
+
+ <p>This is for a file that has Perl code and classic BSD
+ code in it:</p>
+ <pre class="programlisting">
+License: GPL-2+ or Artistic-2.0, and BSD
+</pre>A <tt class="literal">GPL-2+</tt> work with the
+ <tt class="literal">OpenSSL</tt> exception is in effect a
+ dual-licensed work that can be redistributed either under
+ the <tt class="literal">GPL-2+</tt>, or under the
+ <tt class="literal">GPL-2+</tt> with the <tt class=
+ "literal">OpenSSL</tt> exception. It is thus expressed as
+ <tt class="literal">GPL-2+ with OpenSSL exception</tt>:
+ <pre class="programlisting">
+License: GPL-2+ with OpenSSL exception
+ This program is free software; you can redistribute it
+ and/or modify it under the terms of the GNU General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later
+ version.
+ .
+ In addition, as a special exception, the author of this
+ 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
+ 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,
+ delete this exception statement from your version.
+ .
+ This program is distributed in the hope that it will be
+ useful, but WITHOUT ANY WARRANTY; without even the implied
+ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
+ PURPOSE. See the GNU General Public License for more
+ details.
+ .
+ You should have received a copy of the GNU General Public
+ License along with this package; if not, write to the Free
+ Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+ Boston, MA 02110-1301 USA
+ .
+ On Debian systems, the full text of the GNU General Public
+ License version 2 can be found in the file
+ `/usr/share/common-licenses/GPL-2'.
+</pre>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h3 class="section"><a name="spdx" id="spdx">SPDX</a></h3>
+
+ <p><a href="http://spdx.org/" target="_top">SPDX</a> is an
+ attempt to standardize a format for communicating the
+ components, licenses and copyrights associated with a
+ software package. It and the machine-readable <tt class=
+ "filename">debian/copyright</tt> format attempt to be
+ somewhat compatible. However, the two formats have
+ different aims, and so the formats are different. The
+ <a href="http://wiki.debian.org/Proposals/CopyrightFormat"
+ target="_top">DEP5 wiki page</a> will be used to track the
+ differences.</p>
+ </div>
+ </div>
+
+ <div class="section">
+ <hr>
+
+ <h2 class="section"><a name="examples" id=
+ "examples">Examples</a></h2>
+
+ <div class="example">
+ <a name="AEN462" id="AEN462"></a>
+
+ <p><b>Example 3. Simple</b></p>
+
+ <p>A possible <tt class="filename">debian/copyright</tt>
+ file for the program <span class="QUOTE">"X
+ Solitaire"</span> distributed in the Debian source package
+ <tt class="literal">xsol</tt>:</p>
+ <pre class="programlisting">
+Format: <VERSIONED_FORMAT_URL>
+Upstream-Name: X Solitaire
+Source: ftp://ftp.example.com/pub/games
+
+Files: *
+Copyright: Copyright 1998 John Doe <jdoe at example.com>
+License: GPL-2+
+ This program is free software; you can redistribute it
+ and/or modify it under the terms of the GNU General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later
+ version.
+ .
+ This program is distributed in the hope that it will be
+ useful, but WITHOUT ANY WARRANTY; without even the implied
+ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
+ PURPOSE. See the GNU General Public License for more
+ details.
+ .
+ You should have received a copy of the GNU General Public
+ License along with this package; if not, write to the Free
+ Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+ Boston, MA 02110-1301 USA
+ .
+ On Debian systems, the full text of the GNU General Public
+ License version 2 can be found in the file
+ `/usr/share/common-licenses/GPL-2'.
+
+Files: debian/*
+Copyright: Copyright 1998 Jane Smith <jsmith at example.net>
+License:
+ [LICENSE TEXT]
+</pre>
+ </div>
+
+ <div class="example">
+ <a name="AEN469" id="AEN469"></a>
+
+ <p><b>Example 4. Complex</b></p>
+
+ <p>A possible <tt class="filename">debian/copyright</tt>
+ file for the program <span class="QUOTE">"Planet
+ Venus"</span>, distributed in the Debian source package
+ <tt class="literal">planet-venus</tt>:</p>
+ <pre class="programlisting">
+Format: <VERSIONED_FORMAT_URL>
+Upstream-Name: Planet Venus
+Upstream-Contact: John Doe <jdoe at example.com>
+Source: http://www.example.com/code/venus
+
+Files: *
+Copyright: 2008, John Doe <jdoe at example.com>
+ 2007, Jane Smith <jsmith at example.org>
+ 2007, Joe Average <joe at example.org>
+ 2007, J. Random User <jr at users.example.com>
+License: PSF-2
+ [LICENSE TEXT]
+
+Files: debian/*
+Copyright: 2008, Dan Developer <dan at debian.example.com>
+License:
+ 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
+ preserved.
+
+Files: debian/patches/theme-diveintomark.patch
+Copyright: 2008, Joe Hacker <hack at example.org>
+License: GPL-2+
+ [LICENSE TEXT]
+
+Files: planet/vendor/compat_logging/*
+Copyright: 2002, Mark Smith <msmith at example.org>
+License: MIT
+ [LICENSE TEXT]
+
+Files: planet/vendor/httplib2/*
+Copyright: 2006, John Brown <brown at example.org>
+License: MIT2
+ Unspecified MIT style license.
+
+Files: planet/vendor/feedparser.py
+Copyright: 2007, Mike Smith <mike at example.org>
+License: PSF-2
+ [LICENSE TEXT]
+
+Files: planet/vendor/htmltmpl.py
+Copyright: 2004, Thomas Brown <coder at example.org>
+License: GPL-2+
+ This program is free software; you can redistribute it
+ and/or modify it under the terms of the GNU General Public
+ License as published by the Free Software Foundation; either
+ version 2 of the License, or (at your option) any later
+ version.
+ .
+ This program is distributed in the hope that it will be
+ useful, but WITHOUT ANY WARRANTY; without even the implied
+ warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
+ PURPOSE. See the GNU General Public License for more
+ details.
+ .
+ You should have received a copy of the GNU General Public
+ License along with this package; if not, write to the Free
+ Software Foundation, Inc., 51 Franklin St, Fifth Floor,
+ Boston, MA 02110-1301 USA
+ .
+ On Debian systems, the full text of the GNU General Public
+ License version 2 can be found in the file
+ `/usr/share/common-licenses/GPL-2'.
+</pre>
+ </div>
+ </div>
+ </div>
More information about the dep-commits
mailing list