Date: Thu, 26 Jul 2012 09:39:57 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Oliver Fromme <olli@lurza.secnetix.de> Cc: FreeBSD Ports <ports@FreeBSD.org>, Baptiste Daroussin <bapt@FreeBSD.org>, Scot Hetzel <swhetzel@gmail.com>, freebsd-ports <freebsd-ports@FreeBSD.org>, Jase Thew <jase@FreeBSD.org> Subject: Re: Question about new options framework (regression?) Message-ID: <501172DD.3080000@FreeBSD.org> In-Reply-To: <201207261441.q6QEfAY9002147@lurza.secnetix.de> References: <201207261441.q6QEfAY9002147@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On 7/26/2012 7:41 AM, Oliver Fromme wrote:
>
> Jase Thew wrote:
> > On 25/07/2012 23:57, Baptiste Daroussin wrote:
> > > because the priority goes to global to specific and the most specific is the
> > > options file.
> > >
> > > if most people want the options file to not have the final priority, why not,
> > > can others spread their opinion here?
> >
> > I can't see why it would be of benefit for saved options to override
> > anything passed to make (either env or as an arg), as one of the reasons
> > you're likely to be passing them is to override any saved settings in
> > the first place.
> >
> > Please consider reverting back to the established and I daresay,
> > expected behaviour.
>
> I agree with Jase.
>
> Actually I'm not sure if PORTS_DBDIR should override make.conf
> or vice versa. I don't know which one should be regarded as
> more specific.
Traditionally the precedence has been:
make.conf < OPTIONS < command line
The reason is that you want to set global options as high up as
possible, and then be able to override things for specific ports, and
specific builds.
We were promised that this would work with the new OPTIONS, it's
disappointing to here that it isn't.
> But anything specified on the commandline is definitely more
> specific than PORTS_DBDIR and should override anything else.
Right.
> One way to do that would be to introduce another pair of
> variables, e.g. OVERRIDE_SET and OVERRIDE_UNSET, so you could
> type: make OVERRIDE_SET=STATIC
That shouldn't be necessary. The code should DTRT, as it did previously.
Doug
--
Change is hard.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?501172DD.3080000>