Adam Kennedy wrote:
> Can I ask the obvious question of why on earth you have a CPAN release
> that is incompatible with bleadperl?
The XS code that is in the CPAN release is C code in bleadperl core (and has
been since 5.9.1?). The CPAN release is intended only as a compatibility module
for earlier releases of Perl to remain compatible with v5.10.0. I literally
want the CPAN release to be a NOOP install under bleadperl or better, which I
have figured out how to do, BTW:
--- Build.PL (revision 396)
+++ Build.PL (local)
@@ -66,6 +66,14 @@
['lib/version/vxs.*'];
}
+if ( $] >= 5.009 ) { # already included in bleadperl
+ $build_arguments{c_source} = '';
+ $build_arguments{pm_files} = {};
+ $build_arguments{xs_files} = {};
+ $build_arguments{add_to_cleanup} = [];
+ $build_arguments{manpages} = {};
+}
+
my $m = $class->new(%build_arguments);
$m->create_build_script;
and a matching set of changes for the Makefile.PL...
> What happens after 5.10.0 comes out and you need to fix a bug?
This is true of any feature in the core and if it was a serious enough problem,
it would require v5.10.1. However, the version object XS/C code has been
largely unchanged for more than a year (with the sole exception of the recent
LOCALE-related change), so I'm not very worried about that side. All of the
$VERSION++ changes to the CPAN release have been focused on getting the pure
Perl release right on as many platforms and releases of Perl as possible.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Blvd
Suite H
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
