On Tue, 15 Apr 2014 13:41:52 -0400 Joey Hess <jo...@debian.org> wrote: > This leaves the question of how to do it; > debhelper knows when a package has a autoconf configure script, but does > not currently do anything to detect use of automake.
Is it a problem if it sets VERBOSE=1 when it shouldn't? I would suggest making dh_auto_test set that environment variable (so it's only the test suite, nothing else), and for it to only do so when autoconf has been detected during a "make check" run (which is the target supported by automake to run the test suite; so if it's not an automake package, and the test suite is on a different target, then it doesn't do harm). That only leaves the possibility for non-automake packages which would misbehave when running "make check" with that environment variable set. In my opinion, this is unlikely enough that it does not outweigh the benefit of doing it for automake packages. -- It is easy to love a country that is famous for chocolate and beer -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
