On Tue, Mar 22, 2011 at 6:12 PM, Ryan Schmidt <[email protected]> wrote: > It sounds like Lars' situation is that perl5.8 did *not* get deactivated. > Unfortunately, with the way the upgrade to perl 5.12 was handled, this *is* > normal (all users will experience this problem), and requires the user to > manually deactivate perl5.8, before proceeding to activate the new perl5. > >
I could just be remembering wrong, but i though in my case that after I got the same error as Lars, macports continued onto the next step, which was removing the old version of perl5 (5.8). Possibly this is because I used the -u switch? But I could just have it mixed up in my head. Scott _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
