On Thu, 15 May 2008, Niko Tyni wrote:
> Hi p5p,
>
> we're currently doing the 5.8.8 -> 5.10.0 transition in Debian, and the
> binary incompatibility in the XS module interface is biting us in an
> unexpected way.
>
> In a nutshell, it's possible during the upgrade to temporarily end up
> in a state where perl is still 5.8.8, but some XS modules are already
> the new ones (ie. built for 5.10.0).
The default perl installation was deliberately designed to avoid just this
problem by including a version-specific directory-path in
$Config{vendorarch}. That way perl-5.8.8 would not try to load
incompatible perl-5.10.0 modules. Debian's build script deliberately does
not include a version-specific $Config{vendorarch}. It might be worth
reviewing that decision.
Changing 5.10.0's $Config{vendorarch} to include the string "5.10" (much
as is done for $Config{archlib} aleady) might solve this problem. Or at
least it might cause the failure to appear earlier and in a way that is
easier to trap gracefully.
> Details on the Debian issue can be found at <http://bugs.debian.org/479711>,
--
Andy Dougherty [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
