Apple's Mac OS X Update Breaks Perl

mir writes "It looks like if you use CPAN to install modules, Apple's latest security update might just have broken your Perl. According to Tatsuhiko Miyagawa 'The Security Update brings (old) IO.bundle with version 1.22 but your IO.pm has been updated to the latest 1.23 on CPAN shell. (But hey, 1.23 was released in 2006...Why do you bring that ancient version back, Apple!?)'."

Comments

Fighting over the same file

[Ed Avis]

Why are Apple's updater and Perl's CPAN shell both trying to update the same file? If the file's there as part of the Apple OS then only the OS's package manager should touch it, and Perl should leave it alone (installing its own version in /usr/local if necessary). It's exactly the same on Linux distributions: the CPAN shell doesn't try to mess with the system perl which is updated using rpm or dpkg.

Re:Fighting over the same file

[99BottlesOfBeerInMyF]

We don't exactly have "package managers" in OS X.

Sure we do, a bunch of them. That's kind of the problem.

Anything you really want to actually work with, you have to maintain yourself

That's a bit of an overstatement. Anything you want a cutting edge version of you'd do well to install and maintain yourself outside of Apple's update path, but for most people just using the Apple installed versions is fine.

Re:Fighting over the same file

[Alrescha]

"Why are Apple's updater and Perl's CPAN shell both trying to update the same file? If the file's there as part of the Apple OS then only the OS's package manager should touch it, and Perl should leave it alone (installing its own version in /usr/local if necessary)."

Why must we learn these lessons again and again? Back in the beginning of time (1983), we learned the following:

Rule #1: Never change *anything* that [vendor] sends you

Rule #2: Always keep your stuff separate from [vendor]

(thank you Melinda)