Wouter Verhelst <[EMAIL PROTECTED]> writes: > On Fri, Jun 29, 2007 at 11:11:04PM +0200, Bill Allombert wrote: >> One of the issue is that tools like sbuild and pbuilder which want to >> take advantage of the Build-Depends-Indep split needs to know whether >> dpkg-buildpackage will call debian/rules build or build-arch. > > It needs to know no such thing. It just needs to know that if it runs > "dpkg-buildpackage -b", only .debs will be generated, and if it runs > "dpkg-buildpackage -B", all debs apart from the _all.debs will be > generated. How exactly this happens is of no concern to sbuild.
It does when "Build-Depends" is used as specified in policy and not like it is (brokenly) used now: Policy 7.6: | Build-Depends, Build-Conflicts | | The Build-Depends and Build-Conflicts fields must be satisfied | when any of the following targets is invoked: build, clean, | binary, binary-arch, build-arch, build-indep and binary-indep. | | Build-Depends-Indep, Build-Conflicts-Indep | | The Build-Depends-Indep and Build-Conflicts-Indep fields must be | satisfied when any of the following targets is invoked: build, | build-indep, binary and binary-indep. That means that is -b is used or if the package does NOT support build-arch then sbuild must install Build-Depends-Indep as well. If build-arch remains optional and policy for Build-Depends remains unchanged then sbuild must now. Making build-arch required or changing the meaning of Build-Depends to the broken use we have now resolves this. I favor making build-arch required. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]