From owner-freebsd-questions@FreeBSD.ORG Mon Nov 12 18:53:46 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9840E16A420 for ; Mon, 12 Nov 2007 18:53:46 +0000 (UTC) (envelope-from fbsd06+QF=9eda887d@mlists.homeunix.com) Received: from turtle-out.mxes.net (turtle-out.mxes.net [216.86.168.191]) by mx1.freebsd.org (Postfix) with ESMTP id 6B39813C4B5 for ; Mon, 12 Nov 2007 18:53:46 +0000 (UTC) (envelope-from fbsd06+QF=9eda887d@mlists.homeunix.com) Received: from mxout-04.mxes.net (mxout-04.mxes.net [216.86.168.179]) by turtle-in.mxes.net (Postfix) with ESMTP id 2DE121646E7 for ; Mon, 12 Nov 2007 13:35:19 -0500 (EST) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id 92C7ED0502 for ; Mon, 12 Nov 2007 13:35:04 -0500 (EST) Date: Mon, 12 Nov 2007 18:35:02 +0000 From: RW To: freebsd-questions@freebsd.org 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> X-Mailer: Claws Mail 3.0.2 (GTK+ 2.12.1; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Ports with GUI configs X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2007 18:53:46 -0000 On Mon, 12 Nov 2007 08:14:02 -0800 "Mark D. Foster" 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