Problems using portupgrade to recompile all ports

[Matthew Seaman]

On Thu, Jan 15, 2004 at 10:03:31AM -0500, Scott I. Remick wrote:

> So... my ultimate question is: how do you pros handle situations like this? 
> Is there a trick I'm missing?

Work out what went wrong, fix it and then just run:

    # portupgrade -af '<2004-01-15'

which does a forced update of all packages installed before the given
date.  (Note: -R and -r are unnecessary with -a).  Rinse,
repeat. Until all your ports are up to date.

Usually ports problems are either inability to download the required
distfiles or a temporary SNAFU by the port maintainer/committer.  In
most cases it suffices to wait a few hours or days, re-cvsup the ports
tree and start the portupgrade job again.

	Cheers,

	Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040115/5e70cb7f/attachment.bin