From owner-freebsd-questions@FreeBSD.ORG Mon Nov 12 20:37:21 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 8990C16A46D for ; Mon, 12 Nov 2007 20:37:21 +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 mx1.freebsd.org (Postfix) with ESMTP id 6170913C4BF for ; Mon, 12 Nov 2007 20:37:21 +0000 (UTC) (envelope-from fbsd06+QF=9eda887d@mlists.homeunix.com) 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 CACDCD0501 for ; Mon, 12 Nov 2007 15:37:11 -0500 (EST) Date: Mon, 12 Nov 2007 20:37:09 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20071112203709.42decddd@gumby.homeunix.com.> In-Reply-To: <4738A71A.6060100@chuckr.org> References: <2852884D-270A-4879-B960-C10A602E080E@ashleymoran.me.uk> <47387891.2060007@unsane.co.uk> <47387BCA.6080604@foster.cc> <20071112183502.438b44b8@gumby.homeunix.com.> <4738A71A.6060100@chuckr.org> 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 20:37:21 -0000 On Mon, 12 Nov 2007 14:18:50 -0500 Chuck Robey wrote: > > Setting the menus is pretty easy to script, and you can also set > > BATCH to take the default options > > A suggestion I recently made on the ports list would, as a side > effect, make a better solution. I don't see why it would. It wouldn't eliminate the config screens - many, if not most, of the existing options couldn't be handled like that. I find the config screens to be a useful way of keeping on top of new functionality, and it's pretty trivial to get them out of the way at the start of an upgrade. All that's really needed is to add this feature (that portmaster already has) to portupgrade. What I've found to be a more awkward problem is ports with interactive deinstall scripts.