Date: Fri, 29 Jun 2007 19:34:04 -0400 From: Robert Huff <roberthuff@rcn.com> To: freebsd-questions@freebsd.org Subject: running portupgrade -a Message-ID: <18053.38636.915030.238090@jerusalem.litteratus.org> In-Reply-To: <20070629231452.GK18911@tigger.digitaltorque.ca> References: <20070629231452.GK18911@tigger.digitaltorque.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael P. Soulier writes: > As /usr/ports/UPDATING is rather large, it seems impossible to > look for potential issues with every package that you're going to > upgrade. So, is running portupgrade -a a good idea, as you likely > haven't checked for issues for your system? I cannot remember the last time I did this. Why? 1) I update regularly, at least twice a week. (Exception: OpenOffice.) It usually takes an hour or so. 2) portupgrade is not bullet-proof. More than once over the years it's exploded over a single port, with consequences for the pkgdb. Clean-up was sometimes trivial ... and sometimes horrendous. As a result, even when I've checked for known issues I am unintersted in a (supposedly) "fire and forget" process involving (in one case) 600+ ports. Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18053.38636.915030.238090>