- 09 May, 2015 1 commit
-
-
Bill Allombert authored
-
- 08 May, 2015 6 commits
-
-
Bill Allombert authored
-
Bill Allombert authored
Policy: [12.3] recommend to ship additional documentation for package 'pkg' in a separate package 'pkg-doc' and install it into /usr/share/doc/pkg. Wording: Russ Allbery <rra@debian.org> Seconded: Bill Allombert <ballombe@debian.org> Seconded: Charles Plessy <plessy@debian.org> Closes: #106073
-
Russ Allbery authored
Weaken the documentation location to "should" to match previous behavior. Change the example of text documentation from TODOs to FAQs. Clarify that documentation should be installed elsewhere if it is used or read by programs, rather than using the ambiguous term "referenced."
-
Russ Allbery authored
Building on top of Ben's patch, this includes the following changes: * Shared library documentation is called out as a special case of the general rule that documentation should be packaged separately if it's large, recommending installing documentation of any appreciable size in the development package or a separate documentation package rather than the shared library package. * The naming convention for documentation packages (package-doc or package-doc-language) is explicitly stated (but is not a requirement). * package-doc is allowed to put documentation in either /usr/share/doc/package or /usr/share/doc/package-doc, but the former is preferred. package-doc still has to install its own mandatory documentation files (changelog, copyright) in /usr/share/doc/package-doc. * The paragraph about /usr/doc is removed. * Some reorganization and wording tweaks to hopefully make things clearer.
-
Ben Finney authored
Recommend that <package> documentation be installed into /usr/share/doc/<package> even if it's packaged separately. Closes: #106073
-
Bill Allombert authored
-
- 11 Feb, 2015 1 commit
-
-
Bill Allombert authored
Wording: Bill Allombert <ballombe@debian.org> Seconded: Andrey Rahmatullin <wrar@debian.org> Seconded: Lucas Nussbaum <lucas@debian.org> Closes: #770016
-
- 09 Feb, 2015 1 commit
-
-
Bill Allombert authored
Policy: [5.1] empty field values in control files are only permitted in the debian/control file of a source package. Wording: Bill Allombert <ballombe@debian.org> Seconded: Henrique de Moraes Holschuh <hmh@debian.org> Seconded: Andrey Rahmatullin <wrar@debian.org> Closes: #666726
-
- 04 Feb, 2015 1 commit
-
-
Bill Allombert authored
Wording: Matthew Vernon <matthew@debian.org> Seconded: Russ Allbery <rra@debian.org> Seconded: Bill Allombert <ballombe@debian.org> Seconded: Julien Cristau <jcristau@debian.org> Closes: #765499
-
- 31 Jan, 2015 1 commit
-
-
Bill Allombert authored
Wording: Andrey Rahmatullin <wrar@debian.org> Seconded: Bill Allombert <ballombe@debian.org> Seconded: Jakub Wilk <jwilk@debian.org> Seconded: Henrique de Moraes Holschuh <hmh@debian.org> Closes: #555979
-
- 23 Nov, 2014 1 commit
-
-
Bill Allombert authored
-
- 22 Nov, 2014 2 commits
-
-
Bill Allombert authored
-
-
- 17 Nov, 2014 2 commits
-
-
Bill Allombert authored
-
Bill Allombert authored
-
- 15 Nov, 2014 3 commits
-
-
David Bremner authored
Another apparent change in the org-mode exported causes this to show up in the output.
-
David Bremner authored
Apparently these TeX macros were previously ignored, but they are not any longer.
-
David Bremner authored
Emacs 24.4 includes an updated org-mode, which changes the export framework quite a lot. This patch also stops sending errors and warnings to /dev/null, in order to help with debugging.
-
- 10 Nov, 2014 1 commit
-
-
Charles Plessy authored
-
- 09 Nov, 2014 1 commit
-
-
Charles Plessy authored
-
- 17 Sep, 2014 2 commits
-
-
Bill Allombert authored
-
Bill Allombert authored
-
- 09 Sep, 2014 1 commit
-
-
Bill Allombert authored
-
- 07 Aug, 2014 1 commit
-
-
Bill Allombert authored
Wording: Bill Allombert <ballombe@debian.org> Seconded: Arno Töll <arno@debian.org> Seconded: Matthias Urlichs <matthias@urlichs.de> Closes: #491547
-
- 02 Aug, 2014 2 commits
-
-
Bill Allombert authored
-
Bill Allombert authored
Wording: Russ Allbery <rra@debian.org> Seconded: Andrew McMillan <andrew@morphoss.com> Seconded: Gregor Herrmann <gregoa@debian.org> Closes: #593611
-
- 30 Jul, 2014 2 commits
-
-
Bill Allombert authored
-
Bill Allombert authored
Wording: Bill Allombert <ballombe@debian.org> Seconded: Jonas Smedegaard <dr@jones.dk> Seconded: Piotr Ożarowski <piotr@debian.org> Closes: #588497
-
- 20 Jul, 2014 1 commit
-
-
Bill Allombert authored
Added java{5,6,7,8,9}-runtime{,-headless} Removed java1-runtime, java2-runtime Wording: Emmanuel Bourg <ebourg@apache.org> Seconded: Tony Mancill <tmancill@debian.org> Seconded: Bill Allombert <ballombe@debian.org> Closes: #754876
-
- 07 Jul, 2014 1 commit
-
-
Bill Allombert authored
Closes: #753999 Thanks Gabriele Giacone.
-
- 30 Jun, 2014 2 commits
-
-
Bill Allombert authored
Wording: Benedikt Wildenhain. Closes: #753353.
-
Bill Allombert authored
-
- 13 Jun, 2014 2 commits
-
-
Bill Allombert authored
Wording: Niko Tyni <ntyni@debian.org> Seconded: Russ Allbery <rra@debian.org> Seconded: Gregor Herrmann <gregoa@debian.org> Seconded: Axel Beckert <abe@debian.org> Closes: #750017
-
Niko Tyni authored
Having $Config{vendorarch} change between Perl major versions (for multiarch or other reasons) implies that packages using it need a strict dependency on those versions of perl-base that have a compatible search path (@INC). The vast majority of these packages are binary ("XS") modules, where we already require a dependency on the virtual package perlapi-*, provided by perl-base. The name of this virtual package will change when the interface between the Perl interpreter and the modules changes. If we consider @INC part of that interface, we can use the existing mechanism also for the few nonbinary modules using $Config{vendorarch}. This is a new requirement that currently affects six packages in the archive.
-
- 30 May, 2014 4 commits
-
-
Bill Allombert authored
Wording: Niko Tyni <ntyni@debian.org> Seconded: Russ Allbery <rra@debian.org> Seconded: Damyan Ivanov <dmn@debian.org> Closes: #748380
-
Niko Tyni authored
The most pressing need for this is for including the multiarch triplet in vendorarch, but it is also a logical continuation for the $Config{debian_abi} concept introduced earlier. If we ever have to make a binary incompatible change without a major version bump, we'll probably have to change @INC too, at least for locally installed binary modules (sitearch). -
Bill Allombert authored
Wording: Russ Allbery <rra@debian.org> Seconded: Bill Allombert <ballombe@debian.org> Seconded: Jonathan Nieder <jrnieder@gmail.com> Closes: #555980
-
Bill Allombert authored
Wording Bill Allombert <ballombe@debian.org> Seconded: Jonathan Nieder <jrnieder@gmail.com> Seconded: Russ Allbery <rra@debian.org> Closes: #742756
-
- 17 May, 2014 1 commit
-
-
Niko Tyni authored
Move the footnote about the Config module to the first reference The new Config reference was introduced in cc34dcc0 but the footnote wasn't moved accordingly. Wording: Niko Tyni <ntyni@debian.org> Seconded: Russ Allbery <rra@debian.org> Seconded: Damyan Ivanov <dmn@debian.org> Closes: #748479
-