From owner-freebsd-ports@FreeBSD.ORG Sat Apr 19 01:53:30 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 7D21737B401 for ; Sat, 19 Apr 2003 01:53:30 -0700 (PDT) Received: from netgecko.info (netgecko.info [217.160.92.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA07743FCB for ; Sat, 19 Apr 2003 01:53:27 -0700 (PDT) (envelope-from alex.kiesel@document-root.de) Received: from [192.168.1.31] (p508B2A97.dip.t-dialin.net [80.139.42.151]) by netgecko.info (Postfix) with ESMTP id 547FA87FF6; Sat, 19 Apr 2003 10:55:09 +0200 (CEST) From: Alex Kiesel To: Stijn Hoop In-Reply-To: <20030418162439.GA1052@pcwin002.win.tue.nl> References: <20030418101304.GF20941@freepuppy.bellavista.cz> <20030418122910.5a39bb44.lehmann@ans-netz.de> <20030418162439.GA1052@pcwin002.win.tue.nl> Content-Type: text/plain Organization: Message-Id: <1050742402.237.2.camel@detention.home.ahk> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 19 Apr 2003 10:53:22 +0200 Content-Transfer-Encoding: 7bit cc: freebsd-ports@freebsd.org Subject: Re: new target to display options 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, 19 Apr 2003 08:53:30 -0000 On Fri, 2003-04-18 at 18:24, Stijn Hoop wrote: > On Fri, Apr 18, 2003 at 12:29:10PM +0200, Oliver Lehmann wrote: > > Roman Neuhauser wrote: > > > > > pre-fetch, post-fetch... How about a new target, say, "options"? > > > > I would like it. I also suggest to create a "standard" how those > > option-messages have to look. Maybe it's better to create a variable which > > get parsed like: > > > > PORT_OPTIONS= WITHOUT_X11:To build the port w/o X11 support \ > > WITH_PNG:To build the port with PNG support > > > > See also mail/mailman & emulators/xmame for an alternate implementation. I think those two are a little bit too verbose :) and they are not parseable. I think it would be nice to have parseable output that you could easily use in some kind of frontend... Generally this target is a very good idea. Greets, -Alex