Date: Mon, 12 Nov 2007 19:29:13 -0700 From: "Steve Franks" <stevefranks@ieee.org> To: "Ashley Moran" <work@ashleymoran.me.uk> Cc: freebsd-questions@freebsd.org Subject: Re: Ports with GUI configs Message-ID: <539c60b90711121829r3d1ff92fy151c096a1f22f225@mail.gmail.com> 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
Not to mention, as a novice, I've discovered that for 20-60% of all ports, messing with the defaults makes the port fail to build.... Steve On Nov 12, 2007 8:26 AM, Ashley Moran <work@ashleymoran.me.uk> 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. > > 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. > > I've seen this: <http://www.freshports.org/misc/dotfile/>, is it what > I'm after? > > Thanks for any advice > Ashley > > > -- > > blog @ http://aviewfromafar.net/ > linked-in @ http://www.linkedin.com/in/ashleymoran > currently @ work > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- Steve Franks, KE7BTE Staff Engineer La Palma Devices, LLC http://www.lapalmadevices.com (520) 312-0089
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539c60b90711121829r3d1ff92fy151c096a1f22f225>