Date: Sat, 2 Oct 2010 09:49:49 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Thomas Mueller <mueller6727@bellsouth.net> Cc: freebsd-questions@freebsd.org Subject: Re: Massive portupgrade without being interrupted by configuration screens? Message-ID: <AANLkTikrHxMdJnMnXCHn7ON8FSC6BMAvjLvke6-tYPKj@mail.gmail.com> In-Reply-To: <4ca708f4.svuMWmkOCHSjxBDf%mueller6727@bellsouth.net> References: <4ca708f4.svuMWmkOCHSjxBDf%mueller6727@bellsouth.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Oct 2, 2010 at 5:27 AM, Thomas Mueller <mueller6727@bellsouth.net> wrote: > How can one do a massive portupgrade, as with -r or -R, without being int= errupted by options configuration screens for many individual ports? =A0Ide= a is to let it run unattended such as when I might run it starting just bef= ore bedtime. =A0Doing "make config" ahead of time also gives the chance to = recover from a typo at the configuration screen (high risk). > > Best thing I can think of is, using multimedia/ffmpeg as an example, is d= oing a dry run > > portupgrade -Rn multimedia/ffmpeg |& tee -a wouldbe.log > > This would show what other packages would need to be portupgraded and avo= id reconfiguring up-to-date dependencies. =A0Then I would go to each of tho= se directories in the ports tree and run "make config". > > Running "make config-recursive" in /usr/ports/multimedia/ffmpeg would pro= duce configuration screens for all dependencies, including those that are u= p-to-date. > > I tried > > portupgrade -RCn multimedia/ffmpeg |& tee -a wouldbe.log > > but then I got all dependency configuration screens, including those that= were up-to-date, and also the interface didn't work right: I got garbage w= hen trying to respond; it didn't write to the configuration screen but prod= uced non-color garbage to the background. > > Running "make config-recursive" in /usr/ports/multimedia/ffmpeg would con= figure all dependencies, including those that are up-to-date and therefore = not in need of portupgrading, though "make config-recursive" seems appropri= ate for a first build/install of a port. > > But I think there is no perfect way to be sure of doing all "make config"= s in advance, since selectable options could require additional dependencie= s. > > If you try to portupgrade perl to 5.12 and everything that depends on it,= as advised in UPDATING file, date 20100715, you will likely get a lot of c= onfiguration dialog screens: I speak from experience, would surely like a w= ay to do all these "make config"s at the beginning. > > Tom Well, I'm not using portupgrade, but instead ports-mgmt/portmaster: # portmaster --force-config --no-confirm [...] lang/perl5.12 Gets all of the config menus out of the way (--force-config), and doesn't sit waiting for confirmation to proceed with install (--no-confirm). I do this only the first time I build a port, or if I need to change a config option and reinstall. Works for me! -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTikrHxMdJnMnXCHn7ON8FSC6BMAvjLvke6-tYPKj>