Bug#628515: recommending verbose build logs
On Mon, Nov 28, 2011 at 11:37:41AM -0800, Russ Allbery wrote:
> Bill Allombert <Bill.Allombert@math.u-bordeaux1.fr> writes:
> > 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.
> I agree with this. Most packages are already doing the right thing, and I
> think terse logs should be the non-default option.
> What should we do about cases where the upstream build system makes it
> difficult to override the verbosity? In other words, is this a place
> where we should push Debian package maintainers to actually fix the
> upstream build system to make build logs verbose even if upstream doesn't
> support that as an option? I'm thinking, for example, of some of djb's
> public domain software, where the compiler invocation is stored in a shell
> script and therefore doesn't appear usefully in the build output. Or
> should Policy just be saying that packagers should enable the verbose
> option by default if there is one?
We should start by providing instruction on how to turn on verbose log on the
most common build systems and deal with exceptions later. Is there some wiki page
Build systems can be sneaky. For example upgrading automake to 1.11 will
activate terse log by default without notice, so the developpers are in the
painful situation to have to disable a feature they never wanted to activate in
the first place.
Imagine a large red swirl here.