Re: system state after freebsd-update and before portugprade -af

2010-06-15 Thread Matthew Seaman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/06/2010 14:34:43, n dhert wrote: > When doing a major version upgrade of FreeBSD, the last (mandatory) step is > to rebuild and reinstall all third party software (ports) > (# portupgrade -af ) > > I have a system with 750+ ports, I guess the po

Re: system state after freebsd-update and before portugprade -af

2010-06-15 Thread Chris Rees
Clears out the old libs, sorry. Prediction playing up! Sorry for top-posting, Android won't let me quote. There's a bug report on it! On 15 Jun 2010 14:57, "Chris Rees" wrote: You're generally ok until you run make delete-old, which clears out the old kind and hoses any port linked to them. So

Re: system state after freebsd-update and before portugprade -af

2010-06-15 Thread Chris Rees
You're generally ok until you run make delete-old, which clears out the old kind and hoses any port linked to them. Sorry for top-posting, Android won't let me quote. There's a bug report on it! On 15 Jun 2010 14:35, "n dhert" wrote: When doing a major version upgrade of FreeBSD, the last (mand

system state after freebsd-update and before portugprade -af

2010-06-15 Thread n dhert
When doing a major version upgrade of FreeBSD, the last (mandatory) step is to rebuild and reinstall all third party software (ports) (# portupgrade -af ) I have a system with 750+ ports, I guess the portupgrade -af will take something like 30 hours to compile (on a test system with 425 ports port