Date: Mon, 27 Jun 2005 11:37:04 -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: <20050627112833.I11987@dualman.cableone.net> In-Reply-To: <200506271318.18073.list-freebsd-2004@morbius.sent.com> References: <20050625112256.GA32433@lothlorien.nagual.st> <200506271318.18073.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 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. > > Portmanager is a good way to bring your ports up-to-date, but it also rebuilds > all ports that depend on out-of date ports. It's a very slow process if you > have a slow machine and most of your ports were up-to-date already, but try > it for yourself. > > Portupgrade does a pretty good job if you follow UPDATING, and use the gnome > script for major Gnome upgrades. > > If you want to force the rebuilding of all your ports then see pkg_glob(1) and > portupgrade (1) for instructions on how to rebuild ports built after a given > timestamp, as this gives you a restartable method. > _______________________________________________ > 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" > 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. Any help/feedback on this will be GREATLY appreciated. :) Denny White -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (FreeBSD) iD8DBQFCwCs6y0Ty5RZE55oRAj6LAJ4wuENN2VAn5IlWUeRsPVps5nBgcQCgtsRr +YpDWuFkojneBoJkl3qk4Jk= =DrUN -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050627112833.I11987>