alternative options for ports

[Sebastian Schulze Struchtrup]

>>> On Tue, Oct 12, 2004 at 03:51:01PM -0400, Frank Laszlo wrote:
>>> If you've got more *specific* problems with usability (like the batch
>>> build problem above), I'm very interested, as I'm trying to collect
>>> these for doing a new round of fixes for the options support in
>>> bsd.port.mk.
>>>   
>>
>>
>> BTW, has anyone started to impliment the NO_<portname>_OPTIONS feature
>> that was requested?
>>  
>>
> That sounds like a great idea to me, I would definately like to devote 
> some time to implementing such a feature if the demand is there. It 
> doesnt sound like it would be very difficult to acomplish. And I'm 
> glad to see someone shares my feelings on dialog's in ports :)
>
I think there will be some major changes with these config options. A 
global NO_OPTIONS is also planned like David has written.
I understand your problems, too. I have also had this one (or some more) 
times, starting a large portupgrade over night and to see the next 
morning that it has stopped at 9pm inside a dialog.
But I think this is solved by a global NO_OPTIONS setting for those who 
don't like it.

Probably it would be best to wait a few days and check what else needs 
to be changed.

With regard to naming, I would suggest something like NO_MENUCONFIG (if 
this is not yet implemented and used). Just for discussion.
NO_OPTIONS can probably lead to some misunderstanding to build ports 
without anything. But configuration through pkgtools or env variables 
still works.


Sebastian


> Regards,
>    Frank