From owner-freebsd-ports@FreeBSD.ORG Thu Nov 13 17:27:23 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1ECF116A4CE; Thu, 13 Nov 2003 17:27:23 -0800 (PST) Received: from mx2.fillmore-labs.com (lima.fillmore-labs.com [62.138.193.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1720343FE0; Thu, 13 Nov 2003 17:27:22 -0800 (PST) (envelope-from eikemeier@fillmore-labs.com) Received: from pd951ac5e.dip.t-dialin.net ([217.81.172.94] helo=fillmore-labs.com ident=byyt3md68vdueukg) by mx2.fillmore-labs.com with asmtp (TLSv1:AES256-SHA:256) (Exim 4.24; FreeBSD 4.9) id 1AKSk4-000Nwb-Vd; Fri, 14 Nov 2003 02:27:21 +0100 Message-ID: <3FB42F6C.8000706@fillmore-labs.com> Date: Fri, 14 Nov 2003 02:27:08 +0100 From: Oliver Eikemeier MIME-Version: 1.0 To: obrien@FreeBSD.org References: <3FB39FB5.5000209@fillmore-labs.com> <20031113164741.GA33494@dragon.nuxi.com> <3FB40710.8010409@fillmore-labs.com> <20031114011128.GA38924@dragon.nuxi.com> In-Reply-To: <20031114011128.GA38924@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: eikemeier@fillmore-labs.com User-Agent: KMail/1.5.9 Organization: Fillmore Labs GmbH X-Complaints-To: abuse@fillmore-labs.com cc: ports@FreeBSD.org cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: ports/59254: ports that write something after bsd.port.mk X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Nov 2003 01:27:23 -0000 David O'Brien wrote: > On Thu, Nov 13, 2003 at 11:34:56PM +0100, Oliver Eikemeier wrote: > >>You are right with CONFIGURE_TARGET, 359 ports use a workaround, thanks >>again for bringing this up. I'm using this workaround myself in the >>OpenLDAP ports, and PR 52917 seems to deal with it. At least it should >>be easy to remove the workaround from those ports, they all use the >>same assignment, so it's just a simple search-and-replace. > > Maybe we need a knob (USE_NEW_CONFIGURE_TUPLE) or something so that > there is complete consistency in the GNU tuple string. OR make it dependend on GNU_CONFIGURE/HAS_CONFIGURE or use GNU_CONFIGURE= new but we should discuss this as a followup of PR 52917