Why I'm Switching to 5.10

Ovid on 2009-09-26T12:11:03

Like many Perl programmers, I've kept at my "comfortable" level of Perl for a long time. This is partly just not wanting to upgrade, but it's also partly because I want to ensure that code I release to the CPAN works for versions of Perl that most people have installed (which is why I don't worry about 5.005 support that much). However, there are many reasons to switch to 5.10.

But my real reason? Snow Leopard. When I upgraded to Snow Leopard, my system somehow got horribly corrupted. I managed to rebuild my 5.10 installation, but 5.8 wouldn't work because Compress::Raw::Zlib wouldn't work. Once I installed that manually, I found that CPAN wouldn't work because it requires Mac::Files, part of the Mac::Carbon distribution.

Mac::Carbon doesn't install on Snow Leopard with 64-bit Perl. In fact, in going through Pudge's blog entries on this topic, none of the various techniques I tried worked. Lots of google hits related to this, but I found no solutions. I finally gave up and switched to 5.10. All because of one critical module. Maybe this isn't a bad thing?

(Of course, it was real fun to discover that Mac Ports added a new PATH= line to my .bash_profile, putting /opt/local/bin before $HOME/bin.)


Mac::Carbon and Snow Leopard

melo on 2009-09-26T15:43:51

Hi,

the main reason that makes Mac::Carbon not compatible with perl5.10 in Snow Leopard is that perl is compiled as mixed 64bit/32bit and Carbon is a 32bit only API.

If you compile perl5.10 32 bit only, Mac::Carbon should install just fine.

Macports /opt/local/bin

autumnmist on 2009-10-05T16:43:55

Re: (Of course, it was real fun to discover that Mac Ports added a new PATH= line to my .bash_profile, putting /opt/local/bin before $HOME/bin.)

Thanks so much for posting this. I searched .profile, .bashrc and couldn't figure out why /opt/local/bin was taking precedence until I found this post.

Re:Macports /opt/local/bin

Ovid on 2009-10-05T18:21:20

I had opened a ticket for this with macports, but they closed it as they can't reproduce it. Until someone can document clear steps needed to reproduce this, it won't get fixed :/ (which is annoying, but reasonable).