Date: Mon, 12 Nov 2007 16:48:17 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: Ashley Moran <work@ashleymoran.me.uk> Cc: freebsd-questions@freebsd.org Subject: Re: Ports with GUI configs Message-ID: <20071112154817.GA15979@owl.midgard.homeip.net> In-Reply-To: <2852884D-270A-4879-B960-C10A602E080E@ashleymoran.me.uk> References: <2852884D-270A-4879-B960-C10A602E080E@ashleymoran.me.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 12, 2007 at 03:26:00PM +0000, Ashley Moran wrote: > Hi > > I was just wondering, what is the motivation behind the GUI configuration > for some ports? Many people prefer to not have to read every single Makefile in the ports tree just to find out which options are available. It can also be nice having the chosen options automatically saved. > 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. > > The apache22 port is the latest one to join this crowd, although there is > an option to skip the GUI. I'm much happier using WITH_PROXY_MODULES or > whatever, and managing everything in pkgtools.conf. > > What is the best way to pre-configure GUI-configured ports? For example, > if I want to script an installation of several ports. 'make config-recursive' to pop up all the config-dialogs before you start building, or 'make BATCH=yes' to skip all the config-dialogs and just use the standard options. Reading the ports(7) manpage can be helpful to find out this kind of things. > > I've seen this: <http://www.freshports.org/misc/dotfile/>, is it what I'm > after? Doesn't look like it. -- <Insert your favourite quote here.> Erik Trulsson ertr1013@student.uu.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071112154817.GA15979>