From owner-freebsd-ports  Sat Sep  9 10:23:29 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from radon.gryphonsoft.com (mcut-b-167.resnet.purdue.edu [128.211.209.167])
	by hub.freebsd.org (Postfix) with ESMTP id E0C0B37B424
	for <ports@FreeBSD.ORG>; Sat,  9 Sep 2000 10:23:26 -0700 (PDT)
Received: by radon.gryphonsoft.com (Postfix, from userid 1000)
	id 9F63B18A2; Sat,  9 Sep 2000 12:20:33 -0500 (EST)
Date: Sat, 9 Sep 2000 12:20:33 -0500
From: Will Andrews <will@physics.purdue.edu>
To: Neil Blakey-Milner <nbm@mithrandr.moria.org>
Cc: Will Andrews <will@physics.purdue.edu>,
	Steve Price <sprice@hiwaay.net>, FreeBSD Ports <ports@FreeBSD.ORG>
Subject: Re: PortsNG (was Re: Ports Options Paper)
Message-ID: <20000909122033.X632@radon.gryphonsoft.com>
Reply-To: Will Andrews <will@physics.purdue.edu>
Mail-Followup-To: Will Andrews <will@physics.purdue.edu>,
	Neil Blakey-Milner <nbm@mithrandr.moria.org>,
	Steve Price <sprice@hiwaay.net>, FreeBSD Ports <ports@FreeBSD.ORG>
References: <20000903052226.E1205@radon.gryphonsoft.com> <20000909003743.B92984@bonsai.hiwaay.net> <20000909161633.A71013@mithrandr.moria.org> <20000909120428.U632@radon.gryphonsoft.com> <20000909191629.A72757@mithrandr.moria.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <20000909191629.A72757@mithrandr.moria.org>; from nbm@mithrandr.moria.org on Sat, Sep 09, 2000 at 07:16:29PM +0200
X-Operating-System: FreeBSD 4.1-STABLE i386
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Sat, Sep 09, 2000 at 07:16:29PM +0200, Neil Blakey-Milner wrote:
> The old apache13-php3, which served as the inspiration for portconf,
> allowed you to just twiddle options, and it did all the work.

Oh yeah.

> In portconf, it created: option-{pre,post}-{extract,patch,build,install}
> if the option gave that target.  This either (I was undecided, and
> didn't get feedback) makes a line:
> 
> "pre-patch: option1-pre-patch option2-pre-patch"
> 
> or:
> 
> "portconf-pre-patch: option1-pre-patch option2-pre-patch"
> 
> And did the magic.  I think the first one would work fine, due to the
> way make(1) works.  PKGNAME was the main problem, but that can easily be
> solved with the new PKGNAME_SUFFIX stuff.

So, let's say a port has (reiterating):

{
        { !foo, !bar },
        { !foo, bar },
        { foo, !bar },
        { foo, bar },
}

for options.  We'd assign option1 to the first set, option2 to the
second set, and so forth, right?

How would bsd.port.mk account for N number of option sets?

-- 
Will Andrews <will@physics.purdue.edu> <will@FreeBSD.org>
GCS/E/S @d- s+:+ a--- C++ UB++++$ P+ L- E--- W+ N-- !o ?K w---
O- M+ V- PS+ PE++ Y+ PGP+>+++ t++ 5 X+ R+ tv+ b++ DI+++ D+ 
G++ e>++++ h! r- y?


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message