control: tag -1 +patch Hello, I've reviewed the discussion in #628515 and #680686, and it looks to me that we have a consensus that package builds should be verbose by default. There are dissenting opinions, but debhelper has implemented verbosity by default, and the other options require substantial work in dpkg-buildpackage, sbuild and other tools -- work which is not being done. I am therefore seeking seconds for the following patch. In seconding this, please remember that to second something is not simply to say that you agree with the change, but also to indicate agreement with my judgement that the change reflects project consensus. About the name: Raphael mentioned that dpkg supports DEB_BUILD_OPTIONS=maintainer-build but I note that what he meant is that the /dpkg source package/ supports this option in its rules file, not that the /dpkg program/ pays it any attention. Also, codesearch reveals that the dpkg source package is unique in using the string 'maintainer-build'. Let's standardise on the shorter 'terse'. > diff --git a/policy/ch-source.rst b/policy/ch-source.rst > index 9e7d79c..83721f5 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 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