From owner-freebsd-ports@FreeBSD.ORG  Thu Nov 13 15:27:36 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
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 CEA0416A4CE; Thu, 13 Nov 2003 15:27:36 -0800 (PST)
Received: from obsecurity.dyndns.org
	(adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 9643343F85; Thu, 13 Nov 2003 15:27:35 -0800 (PST)
	(envelope-from kris@obsecurity.org)
Received: by obsecurity.dyndns.org (Postfix, from userid 1000)
	id E7BD066B0C; Thu, 13 Nov 2003 15:27:30 -0800 (PST)
Date: Thu, 13 Nov 2003 15:27:30 -0800
From: Kris Kennaway <kris@obsecurity.org>
To: Oliver Eikemeier <eikemeier@fillmore-labs.com>
Message-ID: <20031113232730.GA56021@xor.obsecurity.org>
References: <3FB39FB5.5000209@fillmore-labs.com>
	<20031113164741.GA33494@dragon.nuxi.com> <3FB40710.8010409@fillmore-labs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FB40710.8010409@fillmore-labs.com>
User-Agent: Mutt/1.4.1i
cc: ports@FreeBSD.org
cc: FreeBSD-gnats-submit@FreeBSD.org
cc: obrien@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 <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Nov 2003 23:27:37 -0000

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.

Unfortunately, that PR causes many more problems than it solves, and
the originator has not responded to requests to work on it.

Kris