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

Scott Webster sewebster at gmail.com
Wed Mar 23 11:11:46 PDT 2011

On Wed, Mar 23, 2011 at 10:46 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
> 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.

Right.  This is likely not important enough to continue discussing...
but, explicitly, what happened for me, I think, is that it (1) failed
to install 5.12 because of the file conflicts, and then (2)
deactivated 5.8.  At this point the port command was finished and I
was back at the prompt.  Now, though, the "problem" was already solved
by 5.8 being deactivated, so all you have to do is retry activating
5.12, or just run port upgrade outdated again etc.  Anyway, clearly
this was not an ideal way to have the upgrade go!


More information about the macports-users mailing list