I'm seconding the last version too.
According to the same codesearch link there are 164 packages now, let's
move this forward.
--
WBR, wRAR
signature.asc
Description: PGP signature
Hi,
Quoting Russ Allbery (2014-08-26 23:51:08)
I think that it is a good idea. Here is a draft patch.
When writing this patch, I became unsure if “*-doc” packages are the best
description for the binary packages that will not be built.
probably in many cases but while it would not make
Johannes Schauer j.scha...@email.de writes:
Quoting Russ Allbery (2014-08-26 23:51:08)
This tag says not to build any separate binary packages that
contain only documentation, and ideally to skip any time- or
resource-consuming build steps that only generate documentation.
Hi,
Quoting Russ Allbery (2014-08-27 17:21:05)
This is back to the problem of ambiguity with changelog, copyright, etc. Hm.
How about:
This tag says to skip any build steps that only generate package
documentation. Required files such as copyright and changelog files must
Le Wed, Aug 27, 2014 at 08:21:05AM -0700, Russ Allbery a écrit :
How about:
This tag says to skip any build steps that only generate package
documentation. Required files such as copyright and changelog files
must still be generated and put in the package, but other generated
Le Mon, Aug 25, 2014 at 06:06:01AM +0200, Johannes Schauer a écrit :
please consider adding nodoc as a possible DEB_BUILD_OPTIONS value to
§ 4.9.1 [1].
The value nodoc or nodocs is currently used in 72 source packages
according to [2]. Documenting nodoc in policy would avoid the
confusion
Charles Plessy ple...@debian.org writes:
I think that it is a good idea. Here is a draft patch.
When writing this patch, I became unsure if “*-doc” packages are the
best description for the binary packages that will not be built. Should
it be any package in the “documentation” section
Hi,
Johannes Schauer wrote:
please consider adding nodoc as a possible DEB_BUILD_OPTIONS value to
§ 4.9.1 [1].
[...]
When bootstrapping, a common approach is to do a build without documentation
to
be able to drop the build dependencies on documentation building tools. This
is
why the
Hi,
Quoting Jonathan Nieder (2014-08-25 20:35:34)
When bootstrapping, a common approach is to do a build without
documentation to be able to drop the build dependencies on documentation
building tools. This is why the build profile name nodoc exists which, if
enabled, allows builds
Johannes Schauer wrote:
Quoting Jonathan Nieder (2014-08-25 20:35:34)
Johannes Schauer wrote:
When bootstrapping, a common approach is to do a build without
documentation to be able to drop the build dependencies on documentation
building tools. This is why the build profile name nodoc
Package: debian-policy
Severity: wishlist
Hi,
please consider adding nodoc as a possible DEB_BUILD_OPTIONS value to
§ 4.9.1 [1].
The value nodoc or nodocs is currently used in 72 source packages
according to [2]. Documenting nodoc in policy would avoid the
confusion between the two. The
11 matches
Mail list logo
