Question

We have a server farm that we are slowly migrating to a new version of Perl (5.12.1). We are currently running 5.8.5. The OS will be upgraded from RedHat 4 to RedHat 5 as well, but RedHat 5 is still back on Perl 5.8.8. Thus for a while in our source tree we’ll be supporting two versions of Perl.

I have been told to install the new version of Perl into our source tree, and also all of the CPAN modules we currently use. I was actualy told to ‘compile’ the modules with the correct version of Perl. I’m confused by this. Do some modules actually configure themselves differently for different versions of Perl? Given this, I assume I should configure a CPAN directory for each version of Perl in our tree?

Any information or ‘gotchas’ about this scenario?

Edit: As an additional question, will the same cpan directory (pointed to by ~/.cpan) serve for both trees, or should I link in different directories when I’m working in different trees (installing modules)?

Answer 1

Any perl modules that use XS (compiled C code, dynamically loaded) will, in general, only work with the same version of perl that they were compiled with. This is for two reasons:

Reason one is that by default they’re installed into a directory that includes the perl version number, and any other version of perl won’t look into that directory.

Reason two is because the perl API can change between major versions, so even if you were to copy the libraries into the appropriate directory, they might or might not work depending on what features they use, and how different the two versions of perl are. Between 5.8 and 5.12 there are significant differences that are likely to break nearly all code.

This doesn’t apply at all to pure Perl modules, though; they can be copied around freely with very few exceptions. It’s only XS code that’s the issue.