In article <[EMAIL PROTECTED]> (gmane.linux.debian.devel.general) you wrote: > On Fri, Jun 29, 2007 at 12:41:04AM +0300, Guillem Jover wrote: [...] >> I've been pondering on what's the cleanest way to fix it for some time, >> and I tend to agree with Steve about using the make options to test >> for the existence of the targets. But as others have pointed out it's >> not clear why that change was reverted at the time.
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=345;att=0;bug=218893 | -q checks for "up to dateness" ... the next time you ran the test, it | would fail because build-stamp had been touched and dpkg-buildpackage | would incorrectly run build for you instead. > 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. So if you > go that route, the exact criterium used by dpkg-buildpackage need to be > published as an interface. I think that is just wrong. sbuild should not need to know anything about dpkg-buildpackage's internals and there is no need for change here. The currently used and proven interface is: 1. install Build-Depends for running dpkg-buildpackage -B 2. install Build-Depends *and* Build-Indep-Indep for running dpkg-buildpackage differently (e.g without any modifier or with -b) cu andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
