Date: Tue, 28 Jun 2005 10:34:43 -0500 (CDT) From: Denny White <dennyboy@cableone.net> To: RW <list-freebsd-2004@morbius.sent.com> Cc: freebsd-questions@freebsd.org Subject: Re: upgrading all ports Message-ID: <20050628102913.S11401@dualman.cableone.net> In-Reply-To: <200506281213.42727.list-freebsd-2004@morbius.sent.com> References: <20050625112256.GA32433@lothlorien.nagual.st> <200506271318.18073.list-freebsd-2004@morbius.sent.com> <20050627112833.I11987@dualman.cableone.net> <200506281213.42727.list-freebsd-2004@morbius.sent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 28 Jun 2005, RW wrote: > On Monday 27 June 2005 17:37, Denny White wrote: >> On Mon, 27 Jun 2005, RW wrote: >>> On Saturday 25 June 2005 12:22, Dick Hoogendijk wrote: >>>> I want to do a portupgrade on all installed ports. >>>> >>>> What's the right way? >>>> "portupgrade -arR ?" >>>> or >>>> "portupgrade -a" ? >>> >>> AFAIK there is no difference between the two; "-a" means upgrade all >>> ports in the package database, "-Rr" means add in the dependencies and >>> dependent ports based on what's in the database, but these are already >>> covered by -a. New dependencies are built as a side-effect of building >>> out-of-date ports - not through the -R option. >>> >>> There *is* a difference between -FRa and -Fa because -FR is translated >>> into a "make checksum-recursive". Anyone who believes that portupgrade is >>> slower than removing all port and reinstalling has probably been misled >>> by watching portupgrade -FRa which runs "make checksum-recursive" for >>> each installed port and so visits some ports many time. >>> >>> ... >> >> This couldn't have come at a better time for me. >> I really boned things up about 40 hours ago. I was >> getting ready to leave and because I'd been doing >> some learning/experimenting with portupgrade on >> some held ports, I hit the wrong switch. I think >> it was portupgrade -arRF & now, about 40 hours >> later, shortly after returning home, we're still >> going, going, going....... Things are really in >> a mess & I've read the recent posts on this thread >> & can attest, sitting here for several hours, that >> "visits some ports many times" is an understatement. >> It's becoming rediculous & I'm wondering if, at >> some point, when clean is going after something >> else was just upgraded, if I can break out & go >> back with a simple portupgrade -arR & not screw >> things up to badly. > > You can break-out of portupgrade -arRF anytime you like, it's only fetching > distfiles not upgrading anything. Normally portupgrade -Fa will fetch all the > file you needs, but portupgrade -FRa is a bit more thorough. > > Really though you don't need to run with the -F option at all, unless you > can't build online or want to prefetch files. If it's taking 40 hours > though, it probably means that your cache of files is badly out-of-date and > you are getting slow downloads - a clean pass that doesn't fetch anything > shouldn't take more than a hour. > _______________________________________________ > 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 finally broke out of it. I waited until it had done its cleaning & was starting to fetch more files. I did a ls -alt on /var/db/pkg & it was definitely installing/ reinstalling ports. Won't do that again. :) I had wanted to force the upgrade or downgrade, whatever, of several held ports. Now I think maybe it had something to do with me not updating perl the right way. My bad. I went back & reread UPDATING & found what I had missed. I did a man perl-after-upgrade & reread all of that too & followed the instructions. Looks like everything's back to normal. Thanks for the help. Denny White -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwW4cy0Ty5RZE55oRAkAKAKCYmKfN8PabPGawUE5M6FQqZBIm+QCdFCsU MTCJr7cUxTcCipfZH/uDvjY= =h6sQ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050628102913.S11401>