Date: Fri, 30 Jun 2006 14:31:40 -0500 From: David J Brooks <daeg@houston.rr.com> To: freebsd-questions@freebsd.org Cc: "Michael P. Soulier" <msoulier@digitaltorque.ca> Subject: Re: batching port builds Message-ID: <200606301431.40968.daeg@houston.rr.com> In-Reply-To: <20060630182544.GG2111@tigger.digitaltorque.ca> References: <20060630161046.GE2111@tigger.digitaltorque.ca> <200606301131.29593.daeg@houston.rr.com> <20060630182544.GG2111@tigger.digitaltorque.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 30 June 2006 13:25, Michael P. Soulier wrote: > On 30/06/06 David J Brooks said: > > If you do 'make -DBATCH' instead of 'make' - you will use the preset > > defaults for each port with options. Or you can do > > 'make config-recursive' - which will offer you all the option screens for > > the port in whose directory you're currently in and all its dependencies. > > > > See 'man ports' for more information. > > > > To use those with 'portupgrade -a' will probably take some custom > > scripting. > > Ah, so there's no make.conf option for this? If there is, I'm unaware of it. Then again, I rarely use 'portupgrade -a' myself. I start with 'portversion -v -l "<"' and work my way down the list interactively. It's more time consuming, but I tend to learn things along the way. :) David -- Sure God created the world in only six days, but He didn't have an established user-base.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200606301431.40968.daeg>