Ports with GUI configs
Manolis Kiagias
sonicy at otenet.gr
Mon Nov 12 11:04:27 PST 2007
RW wrote:
> On Mon, 12 Nov 2007 08:14:02 -0800
> "Mark D. Foster" <mark at foster.cc> wrote:
>
>
>> Vince wrote:
>>
>>> Ashley Moran wrote:
>>>
>>>
>>>> Hi
>>>>
>>>> I was just wondering, what is the motivation behind the GUI
>>>> configuration for some ports? Simply put, they drive me up the
>>>> wall. I've lost count of the number of times I've come back to a
>>>> big install to find it hanging on a config screen. Possibly I'm
>>>> missing something.
>>>>
>>> I agree though, I often suffer the same problem, coming back after
>>> a few hours to a build that should have finished to find its
>>> sitting on the first dependency.
>>>
>>>
>> Maybe it's been suggested before (in which case I add my vote) but a
>> timeout mechanism would solve this... give the user 10s to provide a
>> keypress else bailout and use the "default" options.
>>
>>
>
> That would involve standing-over the build for hours or days in case
> you miss a 10-second window - it's just not practical IMO.
>
>
> Setting the menus is pretty easy to script, and you can also set BATCH
> to take the default options
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>
>
And in fact you can make all these screens appear before actually compiling:
make config-recursive
(select all wanted options)
make install clean (no more questions asked)
it is all in the manual: man ports
More information about the freebsd-questions
mailing list