Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 0AA759FA434 for ; Sat, 27 Jan 2007 12:34:08 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 50461-03 for ; Sat, 27 Jan 2007 12:34:07 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by postgresql.org (Postfix) with SMTP id 15E029F9F0A for ; Sat, 27 Jan 2007 12:34:06 -0400 (AST) Received: (qmail invoked by alias); 27 Jan 2007 16:27:25 -0000 Received: from ip-90-187-4-143.web.vodafone.de (EHLO colt.pezone.net) [90.187.4.143] by mail.gmx.net (mp020) with SMTP; 27 Jan 2007 17:27:25 +0100 X-Authenticated: #495269 From: Peter Eisentraut To: Bruce Momjian Subject: Re: Change draft gmake control Date: Sat, 27 Jan 2007 17:28:03 +0100 User-Agent: KMail/1.9.5 Cc: pgsql-docs@postgresql.org, PostgreSQL-patches References: <200701271514.l0RFEXK19056@momjian.us> In-Reply-To: <200701271514.l0RFEXK19056@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200701271728.04355.peter_e@gmx.net> X-Y-GMX-Trusted: 0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/21 X-Sequence-Number: 4117 Bruce Momjian wrote: > Nothing, but the point is that draft is a modifier and it isn't clear > > >from that syntax that draft is a modifier and not a target. > > > > Anyway, certainly you could write this to preserve the target: > > > > draft: > > $(MAKE) html DRAFT=Y > > The problem is that the 'gmake' recursion is done, but then returns > and runs the hhml again, so 'gmake draft html' calls "$(MAKE) html > DRAFT=Y" and on return from that, the html is called again and > rebuilds, so it isn't really draft. Well, "gmake draft html" doesn't make any sense anyway, but "gmake draft" by itself does and the new way of writing it is significantly more cumbersome, so I request that this be fixed. -- Peter Eisentraut http://developer.postgresql.org/~petere/