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>
Steve Langasek [Mon, 21 Mar 2011 09:17:14 +0000 (02:17 -0700)]
Fix multiarch FHS exception for i386 in light of recent discussions
The current value of DEB_HOST_GNU_TYPE on i386 is unsuitable for
cross-distro standardization, because it varies according to the default CPU
target of the toolchain. Discussion with the toolchain and dpkg maintainers
yielded an alternative solution, a new dpkg-architecture variable
DEB_HOST_MULTIARCH which is committed to dpkg upstream in commit af3153d09aa3ed5597d6d415e5ab7cc3ba972e7c and will be included in the upload
of dpkg 1.16.0. Update Policy to document this new requirement for
multiarch.
* Add introductory paragraphs for each archive area explaining briefly
the purpose of that archive area. Based on a proposal by CJ
Fearnley. (Closes: #594542)
Update the ldconfig footnote listing /etc/ld.so.conf directories
* Update the ldconfig footnote listing the /etc/ld.so.conf directories
to remove the libc5 compatibility directories and mention the
multiarch triplet directories. Based on a patch by Charles Plessy.
(Closes: #597074)
* Add emacs23 to the build dependencies and remove the files generated
from org source from the revision control repository. Build and clean
files from org source unconditionally. Add Process.{txt,html} to the
list of files generated from org source. (Closes: #594274)
* Move Build-Depends-Indep to Build-Depends (there's no reason to use
-Indep in a package that builds only architecture-independent binary
packages), wrap it, and remove version restrictions that are older
than the version in oldstable.
Russ Allbery [Fri, 20 Aug 2010 22:36:19 +0000 (15:36 -0700)]
Document current behavior of conflicting conffiles
Document that the new package takes over the conffile from the removed
package when the packages conflict, and that the new package may see
left-over configuration files from the old package. Reorder the section
to put the preferred solutions first.
Russ Allbery [Wed, 18 Aug 2010 20:55:34 +0000 (13:55 -0700)]
Clarify required rules in debian/rules
* Use the word "implemented" to describe required targets in
debian/rules, which is clearer about allowing wildcard rules. List
the required rules in their own paragraph rather than with the
paragraph discussing non-interactivity, and explicitly mark all rules
as either required or optional. (Closes: #536790)
Russ Allbery [Thu, 12 Aug 2010 18:23:22 +0000 (11:23 -0700)]
Better define build architecture and host architecture
* Be more verbose in defining the build architecture and the host
architecture and consistently refer to architecture rather than
machine. (Closes: #591857)
projects / debian / debian-policy.git / log