Hello,
On Sun 22 Jul 2018 at 10:58PM +0100, Ian Jackson wrote:
> Are you sure "as verbose as {+reasonably+} possible" would not be
> better ?
>
> Imagine a build that, oh, I don't know, was able to spit megabytes of
> base-64-encoded binaries to its stderr, or something. Obviously
> enablig that is "not what we meant" here but it's the literal meaning
> of the proposed text...
Thank you. This occurred to me last night, but I couldn't come up with a
way to address the issue that was not rather cumbersome.
I think that the use of 'maximally' is fine given that the previous
sentence is now qualified with 'reasonably'.
Here is the revised patch; David and Andrey, hopefully you will renew
your seconds:
> diff --git a/policy/ch-source.rst b/policy/ch-source.rst
> index 9e7d79c..c35e994 100644
> --- a/policy/ch-source.rst
> +++ b/policy/ch-source.rst
> @@ -277,6 +277,13 @@ reproduce the same binary package, all required targets must be
> non-interactive. It also follows that any target that these targets
> depend on must also be non-interactive.
>
> +The package build should be as verbose as reasonably possible, except
> +where the ``terse`` tag is included in ``DEB_BUILD_OPTIONS`` (see
> +:ref:`s-debianrules-options`:). This means that ``debian/rules``
> +should pass to the commands it invokes options that cause them to
> +produce maximally verbose output. For example, the build target
> +should pass ``--disable-silent-rules`` to any configure scripts.
> +
> For packages in the main archive, no required targets may attempt
> network access.
>
> @@ -505,6 +512,12 @@ The meaning of the following tags has been standardized:
> times are long enough and the package build system is robust enough
> to make supporting parallel builds worthwhile.
>
> +``terse``
> + This tag means that the package build will be less verbose than
> + default. For example, ``debian/rules`` might pass options to the
> + package's configure script that cause the compiler to produce less
> + output.
> +
> Unknown flags must be ignored by ``debian/rules``.
>
> The following makefile snippet is an example of how one may implement
--
Sean Whitton
Attachment:
signature.asc
Description: PGP signature