Joshua committed a big update to all of the perl ports and modules in MacPorts today in r94655. (Thanks, Joshua!) As a result when you run "sudo port selfupdate" and "port outdated", you'll find all perl and p5 ports need to be upgraded.
When you upgrade the p5 ports, you may see warning messages like these: ---> Computing dependencies for p5.12-locale-gettext ---> Fetching distfiles for p5.12-locale-gettext ---> Verifying checksum(s) for p5.12-locale-gettext ---> Extracting p5.12-locale-gettext ---> Applying patches to p5.12-locale-gettext ---> Configuring p5.12-locale-gettext ---> Building p5.12-locale-gettext ---> Staging p5.12-locale-gettext into destroot ---> Installing p5.12-locale-gettext @1.50.0_7 ---> Cleaning p5.12-locale-gettext ---> Computing dependencies for p5.12-locale-gettext Warning: Failed to open Portfile from registry for p5.12-locale-gettext @1.50.0_6 ---> Deactivating p5.12-locale-gettext @1.50.0_6 ---> Activating p5.12-locale-gettext @1.50.0_7 ---> Cleaning p5.12-locale-gettext Warning: Failed to open Portfile from registry for p5.12-locale-gettext @1.50.0_6 ---> Uninstalling p5.12-locale-gettext @1.50.0_6 Ignore the warnings; they are harmless. When you originally installed these ports (or any port), a copy of the portfile was placed in the registry. And when you upgrade or uninstall a port, MacPorts tries to use that old copy of the portfile to perform any custom deactivation instructions. But the old p5 portfiles are not compatible with the changes that have just occurred in the perl5 portgroup; therefore MacPorts prints the warnings. You can ignore the warnings because none of the p5 ports contain any custom deactivation instructions. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
