Date: Mon, 12 Nov 2007 18:35:02 +0000 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: Ports with GUI configs Message-ID: <20071112183502.438b44b8@gumby.homeunix.com.> In-Reply-To: <47387BCA.6080604@foster.cc> References: <2852884D-270A-4879-B960-C10A602E080E@ashleymoran.me.uk> <47387891.2060007@unsane.co.uk> <47387BCA.6080604@foster.cc>
index | next in thread | previous in thread | raw e-mail
On Mon, 12 Nov 2007 08:14:02 -0800 "Mark D. Foster" <mark@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 optionshome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071112183502.438b44b8>