On Fri, 8 Feb 2019 04:04:13 +0000 Wookey <wookey@wookware.org> wrote: [...] > Hmm. Looks like there has been a revamp of the templates for > tools. Now the extra build-dep needs to go in > debian/templates/control.tools-versioned.in now. For some reason all > these build-deps seem to have lost their build-profile info (except > for asciidoc). I don't understand why that would be so. We don't want those > extra build-deps in stage1? [...] The single list of Build-Depends was getting hard to manage. So I changed debian/bin/gencontrol.py to extract Build-Depends from each binary package template, qualify them with the architectures and build- profiles specified for that binary package, and append them to Build- Depends-Arch or -Indep as appropriate. So in a binary package template you only need to specify architecture or profile qualifications for a build-dependency if the binary package should sometimes be built without it. Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky
Attachment:
signature.asc
Description: This is a digitally signed message part