Josselin Mouette wrote: > automake 1.11 introduced the concept of “silent rules”. The output looks > much nicer with them, however they are not suitable at all for building > packages, especially on buildds. It sometimes makes a build error much > harder to debug, simply because you can’t see the command lines that are > actually executed. > > The fix is very simple: pass --disable-silent-rules to configure in > Buildsystem/autoconf.pm.
This seems to be rather a matter of taste whether it's liked or not;
whether it's seen as hiding useful information, or eliminating clutter
so real problems can be seen.
Since it has to be manually enabled on a per-package basis, and can be
easily patched if a DD doesn't like upstream's choice, I'm reluctant to
insert debhelper in the middle.
I do wonder why/how the implementation hides command lines on errors.
After all, debhelper defaults to being silent; few users turn on verbose
mode as a matter of course; and yet when debhelper fails to run a
command, it then displays it[1]. Does automake's implementation
hide failing command lines? Do you have an example log? Couldn't doing
so easily be considered a bug in automake?
--
see shy jo
[1] Actually, it just printed out the command name and not its arguments
in some cases. Fixed in git.
signature.asc
Description: Digital signature
