Date: Wed, 04 May 2011 22:51:05 +0100 From: Chris Whitehouse <cwhiteh@onetel.com> To: Chris Brennan <xaero@xaerolimit.net>, User Questions <freebsd-questions@freebsd.org> Subject: Re: A possibly odd upgrade question Message-ID: <4DC1CA49.8060801@onetel.com> In-Reply-To: <BANLkTime92wrMOUhESWVRpLjHGCd9Sc9RA@mail.gmail.com> References: <BANLkTiki_yzeYNGVsSunk0H6j0EY%2BAb2Zg@mail.gmail.com> <20110504142626.539c2b6f@scorpio> <BANLkTime92wrMOUhESWVRpLjHGCd9Sc9RA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04/05/2011 20:53, Chris Brennan wrote: > On Wed, May 4, 2011 at 2:26 PM, Jerry<jerry@seibercom.net> wrote: > > Chris, when I have had to do major rebuilds, I have found >> "portmanager" to be the best tool. It just seems to work. In any case, >> if it were me, I would clean out the /usr/ports/distfiles directory, >> update your ports tree, and then update you OS. When you are finished >> with that fun chore, run; "portmanager -u -l -y -f". Depending on the >> number of ports installed, it might take some time though. Obviously, >> you need portmanager installed first. By the way, if you know you need >> a distfile installed first, something like diablo-jdk or diablo-jre >> that require you to have the distfile all ready in >> the /usr/ports/distfiles directory prior to attempting to build the >> port, then do that prior to updating your system and running >> portmanager. >> > > The problem here (as I have previously mentioned and further discussed in my > reply to Andrew Clarke) is that the most of the ports won't rebuild for > various reasons. I'm pretty handy, but not brilliant. So instead of asking > for my hand to be held by the mailing list, I thought nuking everything I > installed from ports after moving to 8.x would be the smartest move, then > from there reinstall (from a fresh ports tree) only what I need for the > retasked purpose. > _______________________________________________ > 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" > I second Jerry, portmanager is indeed a very effective tool, it's simple and thorough and probably has as good a chance of fixing ports issues as anything. Or used to, I've been trying out tinderbox so haven't used it for a year or so. If you do use portmanager there are a few tricks you can do to make it effectively unattended. However, doesn't -u -f mean rebuild all dependencies of all ports? In which case wouldn't it be just as effective and cleaner for the OP to nuke the lot and rebuild, particularly in view of the retasked purpose. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DC1CA49.8060801>