Rebuild all ports for perl minor version update?
mueller6724 at bellsouth.net
Sun Jun 16 09:53:31 UTC 2013
> They don't really need to be re-built, but it is the safest way to go. I
> never go that way as he risk is EXTREMELY low and the time savings are HUGE.
> I just posted a much quicker way in the thread on Broken SNMP::Info.
> Start with "portmaster p5-". Then go check on the remaining files (not
> directories) under /usr/local/lib/perl5/site_perl/OLD_PERL_VERSION and
> re-build the ports that installed them (pkg_info -W FILENAME to find them).
> Also, the changes to the perl ports were for the exact purpose of
> eliminating the future need to do these rebuilds for minor version updates.
> R. Kevin Oberman, Network Engineer
Reading UPDATING again showed that there was a modification in direcctory structure.
Maybe that's the reason for upgrading all ports that depend on perl.
But then why not go further and upgrade to perl 5.18?
So now I do the massive portmaster upgrade and am stopped by silly little things, like a conflict between the old transmission-gtk2 and the newer version, and later gcc can't make clean because of checksum errors. It didn't know to deinstall the old transmission-gtk2?
So I ran pkg delete transmission-gtk2, knowing it was to be rebuilt to a newer version.
Also, the gcc-4.6.4 upgrade was apparently successful, and no work directory remains for that port.
A long operation can be done while the user is doing other things, like bed, food preparation, eating, outside errands, work on another computer, etc.
More information about the freebsd-ports