Date: Wed, 12 Nov 2003 08:55:59 -0800 From: "Drew Tomlinson" <drew@mykitchentable.net> To: "Jan Grant" <Jan.Grant@bristol.ac.uk>, "William O'Higgins" <william.ohiggins@utoronto.ca> Cc: freebsd-questions@freebsd.org Subject: Re: portupgrade -arR Message-ID: <01bd01c3a93d$db4ef570$6e2a6ba5@lc.ca.gov> References: <20031111173315.GA30896@sillyrabbi.dyndns.org> <Pine.GSO.4.58.0311121030520.24671@mail.ilrt.bris.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message ----- From: "Jan Grant" <Jan.Grant@bristol.ac.uk> Sent: Wednesday, November 12, 2003 2:37 AM > On Tue, 11 Nov 2003, William O'Higgins wrote: > > > Quite foolishly, I ran this command without thinking it through: > > > > portupgrade -arR > > > > It's been running for 15 hours or so now, and I'm wondering how much > > longer it is likely to take? I realize that "that depends" <grin /> > > Well, "that depends"; many ports can be upgraded quickly. However > compilation of C++ is markedly slower than compilation of C, so whenever > you see things like KDE or Qt meeding an upgrade, expect it to take a > while. > > If you use "portversion -v | grep -v =" then you'll see the list of > ports which remain that need updating. (You need to run portsdb after a > cvsup for the output of this, and portupgrade's operation, to be > accurate.) Or you can use the (IMHO) simpler 'portversion -vL=' to get the same information. Cheers, Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01bd01c3a93d$db4ef570$6e2a6ba5>