Date: Tue, 24 Nov 2009 22:29:04 +0100 From: Erik Trulsson <ertr1013@student.uu.se> To: freebsd-questions@freebsd.org Subject: Re: 7.2-STABLE to 8-R Message-ID: <20091124212904.GA32215@owl.midgard.homeip.net> In-Reply-To: <20091124211851.GA79446@comcast.net> References: <20091124154514.GA91657@potato> <200911241725.42229.pieter@degoeje.nl> <20091124163718.GB91657@potato> <4B0C1249.1090600@lazlarlyricon.com> <20091124174025.GC91657@potato> <20091124210948.GC87829@slackbox.xs4all.nl> <20091124211851.GA79446@comcast.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 24, 2009 at 01:18:51PM -0800, Charlie Kester wrote: > On Tue 24 Nov 2009 at 13:09:48 PST Roland Smith wrote: > >On Tue, Nov 24, 2009 at 05:40:25PM +0000, John wrote: > >> > >> Regarding ports, I think I'll take the long route. This box is my main > >> machine, my desktop - and so there are a LOT of ports installed. It will > >> be easier to make portmanager rebuild everything in pristine mode. It > >> will take a long time, but I accept this. Before this is done, I run the > >> built-in routines in /usr/ports - clean out */work/* and distfiles. > > > >I would _strongly_ advise you to make a list of all your current ports, e.g. with > >'portmaster -L >ports.list', deleting all ports and re-installing the ports > >labeled as 'leaf ports' and 'root ports' in ports.list. > > > >While portmaster/-manager do their best, they just cannot cover all the corner > >cases, especially since some ports require extra action (e.g. perl!) There is > >a good chance you'll end up with a big mess like binaries linked to both 7.x > >and 8.x libraries or ports failing to build for mysterious reasons. Both have > >happened to me in the past and are a major PITA to fix. > > > >I've done the complete delete/reinstall run a couple of times now on my > >desktop with ???490 ports installed. > > Can someone remind me once again, when rebuilding all of my ports, what > is the trick for avoiding the options dialogs? I'd like to have this > run largely unattended. I seem to recall someone describing a method to > go through all of them upfront, rather than having the build process > interrupted each time a port wants that input. Use 'make config-recursive' to go through all the option dialogs first. See the ports(7) manpage for other make targets and variables that influence which/how ports are built. > > I know that portupgrade has a batch build option, but unless I'm > mistaken, that skips any ports that need interaction to build. > _______________________________________________ > 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" -- <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?20091124212904.GA32215>