Which ports store/use OPTIONS (/var/db/ports/portname/options)?

[Geoffrey Giesemann]

On Tue, Feb 28, 2006 at 02:39:12AM -0800, Jeremy Chadwick wrote:
> On Tue, Feb 28, 2006 at 09:32:10AM +0100, Clement Laforet wrote:
> > On Mon, Feb 27, 2006 at 12:18:07PM -0500, Chris Shenton wrote:
> > > Other ports don't, like www/apache22.  This is annoying because I have
> > > to remember when I rebuild it, and portupgrade won't get my needed
> > > tweaks like WITH_PROXY_MODULES.
> > > 
> > > For apache22 I've set my needed tweaks in /etc/make.conf but that
> > > doesn't seem the best place, especially since the config names are so
> > > generic, like WITH_SSL_MODULES.
> > 
> > www/apache2* ports can't be converted to OPTIONS since many build time 
> > options are not simple defines.
> > 
> Likewise, www/cgiwrap can't be fully converted to OPTIONS for this
> reason (i.e. supporting a custom logfile location), and the same for
> www/suphp.
> 
> Personally, I've never liked OPTIONS and /var/db/ports.  I consider it
> "another directory I have to worry about", especially if the port
> author changes some of the OPTIONS names between port revisions ("Eh?
> Why is this port building with the wrong settings... *30 minutes later*
> Oh, hrm...").  I'm also not very fond of curses, especially when it
> comes to dealing with it over a serial console that lacks proper
> terminal support.
> 
> Additionally, there needs to be dialog --inputbox support for OPTIONS
> to become useful.
> 

I prefer OPTIONS since you get a list of all of a port's configurables
without having to read the port's Makefile (some Makefiles are neater
than others).

Another thing OPTIONS could/should do is reprompt for a config in the
event that OPTIONS list changes.