'sudo port upgrade outdated' perl5.8->perl5.12 problem

Lars Sonchocky-Helldorf lars.sonchocky-helldorf at hamburg.de
Wed Mar 23 16:47:25 PDT 2011

Am 23.03.2011 um 18:46 schrieb Ryan Schmidt:

> On Mar 23, 2011, at 00:47, Scott Webster wrote:
>> On Tue, Mar 22, 2011 at 6:12 PM, Ryan Schmidt 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.
> Yes, MacPorts would deactivate perl5 @5.8.x_y when upgrading to perl5 @5.12.p_q.
> But MacPorts would not know to deactivate perl5.8 @5.8.x_y first; you must do so manually.

I did some googling and found this:



so the issue seems to be already known. Thanks for your attention and hints!



More information about the macports-users mailing list