From owner-freebsd-ports@FreeBSD.ORG  Sun Oct 12 05:25:29 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 AE0B116A4C1
	for <freebsd-ports@freebsd.org>; Sun, 12 Oct 2003 05:25:29 -0700 (PDT)
Received: from smtp2.netcologne.de (smtp2.netcologne.de [194.8.194.218])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C753243FDF
	for <freebsd-ports@freebsd.org>; Sun, 12 Oct 2003 05:25:28 -0700 (PDT)
	(envelope-from thomas@laurel.tmseck.homedns.org)
Received: from laurel.tmseck.homedns.org (xdsl-213-168-119-110.netcologne.de
	[213.168.119.110])
	by smtp2.netcologne.de (Postfix) with SMTP id A19EB3A1CF
	for <freebsd-ports@freebsd.org>;
	Sun, 12 Oct 2003 14:25:26 +0200 (MEST)
Received: (qmail 654 invoked by uid 1001); 12 Oct 2003 12:11:19 -0000
Date: 12 Oct 2003 12:11:19 -0000
Message-ID: <20031012121119.653.qmail@laurel.tmseck.homedns.org>
From: tmseck-lists@netcologne.de (Thomas-Martin Seck)
To: freebsd-ports@freebsd.org
Organization: private site
In-Reply-To: <C9367B46-FC3D-11D7-8071-000A956B6386@FreeBSD.org>
X-Newsgroups: gmane.os.freebsd.devel.ports
X-Attribution: tms
Subject: Re: Ports conflicts: `lib/libiberty.a'
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: Sun, 12 Oct 2003 12:25:29 -0000

* Ade Lovett <ade@freebsd.org>:

> No.  Please no.  Oh lordy, no.  The maze of options, variables, hacks, 
> and other bits and pieces needs to be reduced, not increased.  It's a 
> staggeringly complex ball of wax already.
> 
> An excellent task for someone who wants to learn A LOT about the ports 
> tree as a single entity would be to run through the entire tree, 
> documenting all these magical flags, and, as a first shot, start 
> cleaning them up.
>
> To take a random case in point, with no finger pointing, things like 
> the use of OpenLDAP has a metric shitload of different, but the same, 
> ways to do things, USE_LDAP, WITH_LDAP, USE_OPENLDAP, WITH_OPENLDAP, 
> WITH_OPENLDAP_VER, LDAP_PORT, etc.. etc..

It would like to see a namespace policy wrt make variables in ports. I
propose that portmgr@ is the authority to define a set of WITH_FOO
variables for "global" use and that every port should be tough to use
these and additionally WITH_PORTNAME_BAR for its own "local" tunables.