Date: Wed, 19 Oct 2005 16:33:14 -0700 From: "Michael C. Shultz" <ringworm01@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: [Fwd: Re: port config questions] Message-ID: <200510191633.14738.ringworm01@gmail.com> In-Reply-To: <4356D354.5020509@childeric.freeserve.co.uk> References: <4356D354.5020509@childeric.freeserve.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 19 October 2005 16:14, Chris wrote: > Sorry, sent to respondent instead of list, resending to list > > Michael C. Shultz wrote: > > On Monday 17 October 2005 14:13, Chris wrote: > >>Q2 Can I tell portupgrade to go through the configs of all the ports it > >>is going to upgrade so that I can set them all in one go and then let > >>portupgrade (or portmanager) get on with things unattended? If not would > >>this be a useful addition to portupgrade functionality? I would like to > >>include options that are in Makefiles as well as 'make config' menus. > > > > Setting BATCH=YES in /etc/make.conf will prevent those blue screens from > > popping up. I'm not sure if this is risky or not but BATCH=YES is a > > permament fixture in my make.conf and haven't noticed any problems yet. > > Does that stop interactive ports being compiled or make them compile > with defaults? bsd.ports.mk says that BATCH mode would make portupgrade > 'skip all the important targets' but I'm not sure what that means. > > I was trying to find a way to walk through all the options, not only in > the blue screen menus but in the options in the various makefiles and > set them before doing the actual upgrade. > > Thanks, > > Chris You could try writing a script that bassed on what's in /var/db/ports puts you into the appropriate port directory and runs make config. Personally I put all my WITH/ WITH_OUT settings into /etc/make.conf and then use BATCH=YES to keep away the blue screens. -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510191633.14738.ringworm01>