On Mon, 23 Jan 2006 19:31:08 +0100, Wouter Verhelst <[EMAIL PROTECTED]> said:
> On Mon, Jan 23, 2006 at 06:59:55PM +0100, Michael Banck wrote: >> On Mon, Jan 23, 2006 at 06:36:40PM +0100, Simon Richter wrote: >> > To summarize the proposals so far: >> > >> > - "Scan debian/rules, invoke build-arch if present". >> > >> > Has been tried, does not work. >> >> AFAIK it is working as long as you assume debian/rules to be a >> Makefile, > No, that is not true. The code to do it that way had been added to > dpkg > 1.10.11 (from 2003!), but was pulled in 1.10.15, with the following > changelog: > dpkg (1.10.15) unstable; urgency=low > * Fix detection of va_copy. > * Back out debian/rules build-arch detection. It is *not* > possible *at all* to detect available targets in a rules file. > Period. > -- Adam Heath <[EMAIL PROTECTED]> Fri, 19 Sep 2003 20:02:19 -0500 Err, don't believe all you read. ====================================================================== __> cat notargetfoo.mk all: @echo nothing to see here __> cat withfoo.mk all: foo @echo something to see here foo: @echo doing foo __> make -n -p -f withfoo.mk | grep foo: >|/dev/null; echo $? 0 __> make -n -p -f notargetfoo.mk | grep foo: >|/dev/null; echo $? 1 ====================================================================== Of course, this kinda presupposes that ./debian/rules is a makefile -- which is what poicy requires it to be. So we can indeed detect if a target foo exists -- just that dpkg folks were trying not to depend on the rules file actually being a makefile, as opposed to something merely having a similar api to a real make file. manoj -- The sheep that fly over your head are soon to land. Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/> 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]