Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Sep 2003 14:11:53 +0000
From:      Philip Reynolds <philip.reynolds@rfc-networks.ie>
To:        freebsd-ports@freebsd.org
Subject:   Re: First attempt at unifying WITH_* options
Message-ID:  <20030929141153.GC94477@rfc-networks.ie>
In-Reply-To: <3F773FEB.6010809@mindspring.com>
References:  <20030928155434.GA770@galgenberg.net> <3F773FEB.6010809@mindspring.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Richard Coleman <richardcoleman@mindspring.com> 86 lines of wisdom included:
> I want to voice my support for adding this type of facility to the port 
> system for FreeBSD.  This is sorely needed.
> 
> I haven't tried the patch yet.  But from a brief glance, it apppears to 
> be exactly what we need.
> 
> We also need a place for the port maintainer to record a summary of the 
> options, as well as any comment that is specific to that option and 
> port.  For instance, if each port had a file "pkg-options", this could 
> print:
> 
> make print-option
>     WITH_TCL - Add tcl support.  Currently experimental.
>     WITH_TK  - Add tk support.  Currently broken.
>     WITH_FOO - Add support for foo.  Developers only.

I hate me too replies, but this seems like definately one of the
biggest shortfalls I've seen with the ports system. It also means
ports can be harder to batch build because they can ignore creating
command-line options and merely allow options handed to the user by
some GUI tool, like dialog(1).
-- 
Philip Reynolds                      | RFC Networks Ltd.
philip.reynolds@rfc-networks.ie      | +353 (0)1 8832063
http://people.rfc-networks.ie/~phil  | www.rfc-networks.ie



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030929141153.GC94477>