Date: Mon, 12 Nov 2007 20:37:09 +0000 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-questions@freebsd.org Subject: Re: Ports with GUI configs 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 12 Nov 2007 14:18:50 -0500 Chuck Robey <chuckr@chuckr.org> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071112203709.42decddd>