From owner-freebsd-ports@FreeBSD.ORG Sat Nov 15 13:17:13 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 2FF0A16A4CE for ; Sat, 15 Nov 2003 13:17:13 -0800 (PST) Received: from outpost.globcon.net (outpost.globcon.net [62.141.88.161]) by mx1.FreeBSD.org (Postfix) with SMTP id 667D743FBD for ; Sat, 15 Nov 2003 13:17:11 -0800 (PST) (envelope-from sergei@FreeBSD.org) Received: (qmail 79506 invoked from network); 15 Nov 2003 21:17:07 -0000 Received: from dom.kolobov.com (HELO kolobov.com) (213.247.180.114) by outpost.globcon.net (62.141.88.161) with SMTP; 15 Nov 2003 21:17:07 -0000 Received: (qmail 909 invoked by uid 911); 15 Nov 2003 21:16:41 -0000 Date: Sun, 16 Nov 2003 00:16:41 +0300 From: Sergei Kolobov To: ports@FreeBSD.org Message-ID: <20031115211641.GA786@chetwood.ru> Mail-Followup-To: ports@FreeBSD.org References: <20031114011128.GA38924@dragon.nuxi.com> <3FB42F6C.8000706@fillmore-labs.com> <3FB40710.8010409@fillmore-labs.com> <20031113232730.GA56021@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8t9RHnE3ZwKMSgU+" Content-Disposition: inline In-Reply-To: <3FB42F6C.8000706@fillmore-labs.com> <20031113232730.GA56021@xor.obsecurity.org> User-Agent: Mutt/1.5.3i X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on outpost.globcon.net X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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: Sat, 15 Nov 2003 21:17:13 -0000 --8t9RHnE3ZwKMSgU+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2003-11-13 at 15:27 -0800, Kris Kennaway wrote: > On Thu, Nov 13, 2003 at 11:34:56PM +0100, Oliver Eikemeier wrote: >=20 > > 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. >=20 > Unfortunately, that PR causes many more problems than it solves, and > the originator has not responded to requests to work on it. It's my PR, and I didn't have a chance to follow-up on it for some time. I am now working on a better patch. On 2003-11-14 at 02:27 +0100, Oliver Eikemeier wrote: > David O'Brien wrote: > >Maybe we need a knob (USE_NEW_CONFIGURE_TUPLE) or something so that > >there is complete consistency in the GNU tuple string. >=20 > OR make it dependend on GNU_CONFIGURE/HAS_CONFIGURE or use > GNU_CONFIGURE=3D new > but we should discuss this as a followup of PR 52917 I think it's quite safe to default to the new CONFIGURE_TARGET value, and use GNU_CONFIGURE=3D old (or, perhaps, 2.13) only for those ports that breaks. I will submit the updated patch shortly. Sergei --8t9RHnE3ZwKMSgU+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/tpe5FOxuaTulNAERAm45AJ9ejHt1vCY+vU7Rb3S2NISbH8vzMgCfe7s3 +CXjHK/Cjh2iHarAWPB/vu4= =VGVM -----END PGP SIGNATURE----- --8t9RHnE3ZwKMSgU+--