Date: Sat, 13 Mar 2004 15:53:50 +0100 From: Oliver Eikemeier <eikemeier@fillmore-labs.com> To: Thomas-Martin Seck <tmseck-lists@netcologne.de> Cc: freebsd-ports@freebsd.org Subject: Re: default OPTIONS aren't the default when BATCH is set Message-ID: <4053207E.4000000@fillmore-labs.com> In-Reply-To: <20040313110145.763.qmail@laurel.tmseck.homedns.org> References: <20040313110145.763.qmail@laurel.tmseck.homedns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thomas-Martin Seck wrote: > * Sergey Matveychuk <sem@ciam.ru> [gmane.os.freebsd.devel.ports]: > > >>There is a workaround while it's not fixed: >>OPTIONS= SOME_DEFAULT "..." on >>WITH_SOME_DEFAULT?= yes > > That looks bogus to me. The ?= does not make sense for variables > which are checked for definedness only (?= is the same as = since you > cannot 'unset' the variable on the commandline) and IMO it is sufficient > to fix the port's options parser to check for WITHOUT_OPTION_FOO when > 'foo' defaults to 'on'. At least this is how I do it in my ports. The whole WITHOUT_* stuff is a misfeature IMHO. What options do I get when I do cd textproc/libxml2; make WITHOUT_PYTHON=yes WITH_SCHEMA=yes WITH_XMLLINT_HIST=yes (which I have in pkgtools.conf). Now I (and lots of other port users) are chasing ports that are early adaptors of buggy features. Not very pleasing. Sorry for the rant, but have you every considered how many man hours of work you generate when you change WITH_X to WITHOUT_X? -Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4053207E.4000000>