Russ Allbery [Mon, 27 Feb 2012 00:53:23 +0000 (16:53 -0800)]
Install copyright-format source without a version
* Ship the copyright-format source as copyright-format.xml.tar.gz
without a version, since it will include all of the versions, not just
the current version.
Russ Allbery [Mon, 27 Feb 2012 00:29:38 +0000 (16:29 -0800)]
Install HTML upgrading-checklist in policy.html directory
* Install the HTML version of upgrading-checklist in the policy.html
directory as upgrading-checklist.html so that it can be deployed on
www.debian.org in a way that will allow links to Policy sections to
work easily. Thanks, Charles Plessy. (Closes: #639663)
For right now, this is done with a bit of a hack to copy the file into
the appropriate directory and to turn the one-page HTML version of it
into a symlink inside the constructed package.
The clean solution will be to make the upgrading checklist an appendix
of Policy, which may be done as part of a DocBook conversion.
Russ Allbery [Sun, 26 Feb 2012 23:50:59 +0000 (15:50 -0800)]
General cleanup of debian/rules
* Strip down and reformat debian/rules to remove unused variables,
references to old files no longer included, use a more standard
layout and standardize variable names, and add comments for better
maintainability.
Russ Allbery [Tue, 21 Feb 2012 20:36:00 +0000 (12:36 -0800)]
General editing pass for the copyright format specification
Add a pointer to DEP-5 in the synopsis and change the verb tense
to present from imperative. Rephrase the introduction to talk about
this document as a specification rather than a proposal.
Explicitly mention Files: * as the way to write a single files
paragraph that covers the entire package.
Mention after one of the examples that the two paragraphs for files
with the same license but different copyright holders could be combined
at the discretion of the document author.
Give the complete correct Format field for the current version of the
document in the description of that field.
Add more explanation for how Disclaimer is used.
Say explicitly that more general files paragraphs should be given
first, followed by more specific overrides.
Update the license list to note that "Universal" is removed from the
version of CC0 when forming the short name, to list the new versions
of the GFDL, and to be more explicit about when to use GFDL-NIV.
Rewording and rephrasing in various places to hopefully make the
text flow better, read more smoothly, and be more idiomatic.
Add multiple additional in-line examples, particularly around the
Files patterns and the formation of license short names.
Charles Plessy [Tue, 21 Feb 2012 18:19:05 +0000 (10:19 -0800)]
DEP-5 updates from further debian-project discussion
Clarify that this document does not supersede or modify the
requirements in Policy and that use of the specification is
optional. Note that a single Files paragraph can apply to the
whole package (rather than using the "all files" wording) and
that only the license and copyright information required by
the Debian archive has to be listed.
Clarify the wording of stand-alone license paragraphs to be
clear that they can be used with exceptions.
Some wording improvements, including making the attributes
listed after the fields lowercase. Fix a few links and the
official keyword of the BSD-3-clause license in some examples.
Russ Allbery [Tue, 21 Feb 2012 18:01:04 +0000 (10:01 -0800)]
Update copyright-format to match the current DEP-5 website text
This addresses multiple issues, clarifications, and reformatting
done as part of the DEP process after the initial import of the
document into the Debian Policy repository.
Russ Allbery [Sun, 1 Jan 2012 17:47:01 +0000 (09:47 -0800)]
Significant rewording of /run, add a separate section
Lift more of the properties of /run into normative text and state
explicitly that the FHS requirements apply to /run and /run/lock.
Add a new section explaining that packages cannot rely on structure
in /run unless they've created it and saying explicitly that packages
must not ship files in /run or /var/run or /var/lock. Reference
that section from the init.d section.
Russ Allbery [Mon, 26 Dec 2011 17:39:17 +0000 (09:39 -0800)]
Document cron job file naming restrictions
Cron job file names need to avoid . and + and should use _ for those
characters instead. Also document a convention for packages that need
to include multiple cron job files.
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
Russ Allbery [Sun, 25 Dec 2011 18:56:52 +0000 (10:56 -0800)]
Do not require initial Debian maintainers be listed in copyright
The documentation of debian/copyright explicitly required the
initial Debian maintainers be listed in the file. That information
is already in the changelog, and they may no longer hold any
copyrights on the remaining files in the package. Drop that
requirement, although the requirement to include copyright and
license information is still in force.
* 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
Russ Allbery [Sun, 25 Dec 2011 18:13:47 +0000 (10:13 -0800)]
Packages in main may not recommend packages in non-free
* 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)
Russ Allbery [Sun, 25 Dec 2011 17:15:17 +0000 (09:15 -0800)]
Clarify policy for symlinks from inside one directory to another
* Clarify the requirements for symlinks from inside one top-level
directory to another and add examples and a rationale. Thanks,
Carsten Hey. (Closes: #626338)
Russ Allbery [Sat, 24 Dec 2011 19:03:49 +0000 (11:03 -0800)]
Clarify the Perl policy documentation rules
The first section about documentation and manual page extensions
only applies to packages generated from the perl source package.
Make that explicit and add a reference to the section discussing
module packages.
Bill Allombert [Mon, 28 Nov 2011 22:49:46 +0000 (23:49 +0100)]
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
Russ Allbery [Mon, 31 Oct 2011 18:00:06 +0000 (11:00 -0700)]
Clarify Description continuation lines must contain non-whitespace
* Clarify that continuation lines of the Description control field must
contain at least one non-whitespace character. Thanks, Guillem Jover.
(Closes: #627490)
Bill Allombert [Thu, 8 Sep 2011 15:20:23 +0000 (17:20 +0200)]
* 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
Bill Allombert [Sat, 28 May 2011 20:37:29 +0000 (22:37 +0200)]
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
Charles Plessy [Sun, 15 May 2011 10:43:16 +0000 (19:43 +0900)]
Normalise the how ‘debian/control’ and ‘.dsc’ files are called.
§5.2 names debian/control files ‘Source package control files’,
and §5.4 names .dsc files ‘Debian source control files’. This patch
ensures that the name ‘Source package control file’ is used only
for debian/control files.
Raphael Hertzog [Mon, 16 May 2011 20:54:34 +0000 (13:54 -0700)]
Architecture in .dsc may now be "any all"
With dpkg >= 1.16.1, the value of the Architecture field in the .dsc
is generated a bit differently.
The goal is to be able to always know when a source package generates an
architecture-independent package. Currently as soon as one binary is
"Architecture: any", the value generated is "any" and we have no way to
know that there are "Architecture: all".
With dpkg >= 1.16.1, the "all" is kept even if there's a binary package
with "any". So the resulting value is then "any all". This allows
wanna-build to know if it must schedule a build for the "Architecure: all"
packages.
Charles Plessy [Tue, 12 Oct 2010 15:14:42 +0000 (00:14 +0900)]
Clarification of the format of control files, Closes: #501930, #593909.
- Specifies field names similarly to RFC 822/5832;
- Distinguishes simple, folded and mulitiline fields;
- Clarifies paragraph separators (#501930);
- The order of paragraphs is significant;
- Fields can have different types or purposes in different control files;
- Moved the description of comments from §5.2 to §5.1;
- Documented that relationship fields can only be folded in debian/control.
Rather than using imperative tense to describe changes as if they
were commit messages, switch to descriptive statements about the
contents of Policy or imperatives for packagers where appropriate.
Only the most recent entries have been reviewed.
Add a cross-reference for Pre-Depends requirements
* Add a cross-reference to the Pre-Depends requirement in 3.5 to section
7.2 where Pre-Depends is defined. Thanks, Mattias Ellert and Jonathan
Nieder. (Closes: #599944)
Jonathan Nieder [Tue, 1 Mar 2011 23:58:48 +0000 (15:58 -0800)]
Add a reminder of Pre-Depends policy to §7.2 "Binary Dependencies"
Section 3.5 says:
You should not specify a Pre-Depends entry for a package before this
has been discussed on the debian-devel mailing list and a consensus
about doing that has been reached.
Add a reminder of this to section 7.2, where the semantics of
Pre-Depends are discussed in more detail.
Requested-by: Mattias Ellert <mattias.ellert@fysast.uu.se> Fixes: http://bugs.debian.org/599944 Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
projects / debian / debian-policy.git / log