What does BATCH=yes really mean? (portmaster vs. bpm)

[Sam Lawrance]

On 14/04/2006, at 5:42 AM, RW wrote:

> On Thursday 13 April 2006 09:57, Sam Lawrance wrote:
>> On 13/04/2006, at 7:23 AM, RW wrote:
>
>>> 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.
>
> As I understand it, "make config" would then just do nothing when  
> BATCH is
> set.
>
> As it stands, someone with BATCH set in a configuration file can still
> run "make config" to set options. IMO that's the way it should be  
> since it's
> an explicit request, rather than a side-effect.
>
> I think it would make sense for portmaster to check for BATCH itself.

I think it's weird for portmaster to try and look in to make  
variables.  Anyway, this all seems to be a moot point - portmaster  
has many interactive steps which seem to be unavoidable.