Date: Tue, 20 Jan 2004 12:06:56 -0500 From: Adam Weinberger <adamw@FreeBSD.org> To: Joe Marcus Clarke <marcus@FreeBSD.org> Cc: Oliver Eikemeier <eikemeier@fillmore-labs.com> Subject: Re: HEADS UP: New bsd.*.mk changes Message-ID: <20040120170656.GA3365@toxic.magnesium.net> In-Reply-To: <1074617147.757.16.camel@gyros> References: <1074590694.85583.20.camel@shumai.marcuscom.com> <400D2939.5090203@fillmore-labs.com> <1074617147.757.16.camel@gyros>
next in thread | previous in thread | raw e-mail | index | archive | help
>> (01.20.2004 @ 1145 PST): Joe Marcus Clarke said, in 7.4K: <<
> On Tue, 2004-01-20 at 08:12, Oliver Eikemeier wrote:
> > Joe Marcus Clarke wrote:
> >
> > > Type: FEATURE
> > >
> > > Title: Add per-port persistent build options with a menu-driven
> > > front-end
> > >
> > > Affects: bsd.port.mk
> > >
> > > Description: Probably one of the most anticipated new features for the
> > > ports system is the ability to have persistent per-port build options.
> > > This new feature adds that functionality as well as a new menu-driven
> > > interface for setting those per-port options. Porters will need to set
> > > the OPTIONS macro in their port's Makefile to a list of WITH_ options
> > > supported by that port. The format is <option> "<description>"
> > > [on|off]. For example: FLEXRESP "Flexible response to events" off.
> > > This says that this port supports a WITH_FLEXRESP option that is not
> > > defined by default. This option's description is, "Flexible response
> > > to events." Multiple options should be chained into the one OPTIONS
> > > macro. NOTE: For OPTIONS to work, you must define OPTIONS before
> > > bsd.port.pre.mk. In order to configure these options, use the
> > > ``config'' target. Doing ``make config'' will pop up a curses-based
> > > dialog which lists all the available options for the given port.
> > > Changes are saved in a per-port directory under PORTS_DBDIR (default:
> > > /var/db/ports). To view configurable options for a port, use the
> > > ``showconfig'' target. To set all port options back to the defaults,
> > > use the ``rmconfig'' target.
> > >
> > > PR:
> > >
> > > Submitted by: eivind
> >
> > Sorry for stepping up so late, but this saves options under
> > ${PORT_DBDIR}/${PORTNAME}/options
> >
> > Lots of ports have the same PORTNAME (ie 'openldap' for
> > net/openldap2[012]-(client|server), 'apache' for russian/apache13,
> > www/apache(13|13-fp|2|21)). Some conflict, but -client/-server don't.
> > Either each port has to set OPTIONSFILE to ${PORT_DBDIR}/${PORTNAME}/something,
> > or we may use LATEST_LINK instead of PORTNAME:
>
> What's the general consensus on this (is there one)? What about ports
> that set NO_LATEST_LINK? In any event, the patch below would need to be
> tested on bento again (uggghh). Since OPTIONSFILE is currently
> overrideable, couldn't porters that have conflicting PORTNAMEs, set this
> file to a unique name. For example:
>
> OPTIONSFILE= ${PORT_DBDIR}/${PORTNAME}/options.mozilla-devel
>
> Wouldn't that satisfy most people? Perhaps we could shorten the public
> OPTIONSFILE to just specify the filename, and do all the grunt work in
> bsd.port.mk...?
>> end of "Re: HEADS UP: New bsd.*.mk changes" from Joe Marcus Clarke <<
Or instead of ${PORTNAME}, use ${.CURDIR:T}.
# Adam
--
Adam Weinberger
adam@vectors.cx // adamw@FreeBSD.org // adamw@magnesium.net
http://www.vectors.cx
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040120170656.GA3365>