* Johannes Schauer <j.schauer@email.de>, 2014-07-09, 16:50:
==> llvm-toolchain-3.4_3.4.1-4.arch-all.unusedbd.real <== automake=1:1.14.1-3 autotools-dev=20140510.1 diffstat=1.58-1 doxygen=1.8.7-1 flex=2.5.39-7 lcov=1.10-1 libtool=2.4.2-1.7 patchutils=0.3.3-1 procps=1:3.3.9-5 sharutils=1:4.14-2 tcl=8.6.0+8 texinfo=5.2.0.dfsg.1-3No, building with DEB_BUILD_OPTIONS=codecoverage enables at least some of them,should build dependencies which the source package only requires after setting some DEB_BUILD_OPTIONS go into Build-Depends?
Probably not, unless it's one of the optioned blessed by Policy §4.9.1. :-)
and applying patches might require the autotools to be re-run, so I think lots of the requirements are sane.My naive assumption was that the Build-Depends line contains a list of binary packages needed to build the package. Not binary packages that might be needed in some situations during the lifetime of a source package?
Agreed. But here I'd recommend regenerating auto* stuff unconditionally, rather than dropping the build-dependencies.
-- Jakub Wilk