Date: Thu, 13 Apr 2006 18:57:39 +1000 From: Sam Lawrance <boris@brooknet.com.au> To: RW <list-freebsd-2004@morbius.sent.com> Cc: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: What does BATCH=yes really mean? (portmaster vs. bpm) Message-ID: <97FBD368-1075-4A9C-9339-8C3524E09DA9@brooknet.com.au> In-Reply-To: <200604122223.43721.list-freebsd-2004@morbius.sent.com> References: <12B35022-89C3-4A5B-ACE3-1C3145974AF9@brooknet.com.au> <200604122223.43721.list-freebsd-2004@morbius.sent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/04/2006, at 7:23 AM, RW wrote: > On Wednesday 12 April 2006 13:18, Sam Lawrance wrote: >> Just hours ago I went to give sysutils/portmaster a try. An OPTIONS >> selection screen appeared on the first run. I then ran the following >> command, thinking I could leave portmaster going and wander off: >> >> portmaster -a -m "BATCH=yes" >> >> Again an OPTIONS dialog appeared. It seems that portmaster was >> running the command 'make BATCH=yes config', which is an interactive >> operation. I'm not sure whether this is incorrect behaviour from the >> 'config' target, or perhaps a deficiency in portmaster. > > BATCH is an instuction not to build ports with IS_INTERACTIVE set - > typically > ports with legal conditions that need to be agreed to. > > It's also used as a hint to build without asking for configuration > options. > This secondary meaning makes no sense with "make config". It seems > to me the > ports system is behaving correctly and portmaster is doing > something odd. I'm not so sure about that. I would have expected it to select the default set of options, just as it would if you were building with BATCH set.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?97FBD368-1075-4A9C-9339-8C3524E09DA9>