On Sun, Nov 27, 2011 at 04:39:33AM -0600, Jonathan Nieder wrote: > Jakub Wilk wrote: > > * Jonathan Nieder <jrnie...@gmail.com>, 2011-11-26, 18:37: > > [...] > >> I do not suspect there is a > >> consensus for this. > > > > Why do you think there is not? > > I was guessing, it seems incorrectly, based on the lack of seconds > or other discussion on this policy proposal. > > >> Some maintainers enjoy reading abbreviated build logs, where error > >> messages and warnings stand out. > > > > Sure, that's why DEB_BUILD_OPTIONS=noverbose was proposed. > > I personally think that DEB_BUILD_OPTIONS=verbose would be better UI, > because the cases where abbreviated build logs are most useful are > during interactive builds (especially interactive builds by novices > who are not accustomed to looking at logs and do not realize they have > a choice about their format but may miss a warning). In > non-interactive builds, it is easy to set an environment variable.
I suppose we want the autobuilders to generate verbose log, but I am not sure if we want the autobuilders to use a non-empty DEB_BUILD_OPTIONS (and whether we can). It is unfortunately possible than a typo in debian/rules only trigger if DEB_BUILD_OPTIONS is set to some value. Most packages will only provide verbose log, so it is rather terse logs that are optionnal. So maybe the option should be DEB_BUILD_OPTIONS=terse. Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org