chromatic discusses binary compatibility with the perl executable. I’m someone who only uses XS modules and hopes to never have to write one. Yet, unlike what seems to be the prevailing fear, I don’t worry about binary compatibility. I don’t worry about upgrades breaking things. I don’t worry that I’m going to have mismatches in executables/libraries.
Why? Continuous integration.
Don’t just grab modules from the CPAN and install them somewhere never to be upgraded until you’re forced to at a huge amount of time and expense. Regularly rebuild everything you use, preferably daily or hourly.
- Install a perl binary and then lock it down. Don’t use site dirs. Have the perl core be inviolate.
- Instead, install to some other directory and point
PERL5LIBat it. Both CPAN and CPANPLUS allow you to configure what you want to be passed to the configuration program. Pass a value for
Build.PLthat points to your directory.
- Set up a build server to use CPAN or CPANPLUS to “install” and build everything. Since your build machine will be rebuilding everything regularly, when you upgrade your perl binary or an XS module, any problems will be quickly identified. Everything being rebuilt in one go means that all binary code will match up and you don’t have to worry about them getting out of sync. Because installing a distribution causes all of that distribution’s tests to be run, you’ll know that that distribution works in your environment.
(If you’re using taint mode and thus cannot use
PERL5LIB, have your build machine build a custom perl executable along with everything else.)
Details for doing this belong in another post. But the point is, if you regularly rebuild all of the CPAN code you use, you don’t need to worry about binary issues.