Dear Mentors, When building packages in clean chroots many configure checks are expected to fail not finding their dependencies. This is fine. Until somebody tries to build the package in a not so clean chroot, where the additional packages present satisfy some of these checks enabling extra features. Or even breaking the build by exposing bugs (see #874600 for an example).
Is adding all possible --disable-whatever options to the configure call a good practice? It clutters debian/rules, isn't easy to do exhaustively in an obviously correct way, but protects against some changes in the build environment. I'm interested in hearing your takes on the issue. -- Thanks, Feri
