Thread: [Module::Build] Pure Perl version objects
Status: Beta
Brought to you by:
kwilliams
Menu
▾
▴
module-build-general
|
From: John P. <jpe...@ro...> - 2006-02-12 17:28:20
|
All - I finally sat down and duplicated the XS version code in Perl and have implemented pure Perl version objects. In order to fully support all of the features (specifically of post 5.8.1 Perl v-strings), it became necessary to add Scalar::Util (1.08 or better) to the prerequisites. Is this going to mean that Module::Build *still* cannot depend on version.pm? ActiveState does include various Scalar::Util releases in both the 5.6.x (non-XS apparently) and 5.8.x (full XS). But ActiveState has been lazy, it seems, as they haven't updated the PPM build machine to anything newer than Module::Build 0.20 (judging from some of the build errors I'm seeing on their web site). Are there any ActiveState'ers on this list that would care to comment why the 5.6.x PPM build machines don't include a newer Module::Build? I don't think I can convert my Build.PL to run with such an ancient beast... The other possibility is that I've already had one person suggest that I convert the version distro to use Module::Install, but I haven't done more than a preliminary look (and I see no evidence that there is the kind of XS support I need). I've released a beta of the new code to CPAN (it should be propagating even now). Any suggestions for how to ensure the split Perl/XS modules could work better would be appreciated. John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 |
|
From: David G. <da...@hy...> - 2006-02-12 18:06:58
|
John Peacock wrote: > All - > > I finally sat down and duplicated the XS version code in Perl and have > implemented pure Perl version objects. In order to fully support all of the Awesome! > ActiveState does include various Scalar::Util releases in both the 5.6.x (non-XS > apparently) and 5.8.x (full XS). But ActiveState has been lazy, it seems, as > they haven't updated the PPM build machine to anything newer than Module::Build > 0.20 (judging from some of the build errors I'm seeing on their web site). Worse is that they haven't updated Scalar::Util from version 1.05 (or 0.06) on their PPM build machine, so *everything* that wants, say, refaddr (Scalar::Util 1.09) doesn't build. There was another round of complaints about it on perlqa. I sent emails recently to both ppm-request and the person listed on perlqa as the maintainer of it and got zero reply. (Not even a "your ticket has been received" reply.) That said, I'd say to go for it. You can probably get Randy Kobes to build up a PPM on the uwinnipeg repository. And with things like CamelPack (http://stennie.org/camelpack/) maybe PPM dependence will be a thing of the past before long anyway. (Now that you've done the pure perl version, of course.) Regards, David |
|
From: Randy K. <ra...@th...> - 2006-02-12 18:55:38
|
On Sun, 12 Feb 2006, David Golden wrote: > John Peacock wrote: >> All - >> >> I finally sat down and duplicated the XS version code in Perl and have >> implemented pure Perl version objects. In order to fully support all of >> the > > Awesome! > >> ActiveState does include various Scalar::Util releases in >> both the 5.6.x (non-XS apparently) and 5.8.x (full XS). >> But ActiveState has been lazy, it seems, as they haven't >> updated the PPM build machine to anything newer than >> Module::Build 0.20 (judging from some of the build errors >> I'm seeing on their web site). > > Worse is that they haven't updated Scalar::Util from > version 1.05 (or 0.06) on their PPM build machine, so > *everything* that wants, say, refaddr (Scalar::Util 1.09) > doesn't build. There was another round of complaints > about it on perlqa. I sent emails recently to both > ppm-request and the person listed on perlqa as the > maintainer of it and got zero reply. (Not even a "your > ticket has been received" reply.) > > That said, I'd say to go for it. You can probably get > Randy Kobes to build up a PPM on the uwinnipeg repository. > And with things like CamelPack > (http://stennie.org/camelpack/) maybe PPM dependence will > be a thing of the past before long anyway. (Now that > you've done the pure perl version, of course.) I've just updated some of these packages on our reposititory that weren't at the most recent (non-developer) version: http://cpan.uwinnipeg.ca/dist/Module-Build http://cpan.uwinnipeg.ca/dist/Scalar-List-Utils http://cpan.uwinnipeg.ca/dist/version -- best regards, Randy |
|
From: John P. <jpe...@ro...> - 2006-02-12 20:55:38
|
Randy Kobes wrote: > http://cpan.uwinnipeg.ca/dist/Module-Build > http://cpan.uwinnipeg.ca/dist/Scalar-List-Utils > http://cpan.uwinnipeg.ca/dist/version That's awsome! Can I add this site to the README file as an alternative source? I wasn't aware of this sites (but that may be because I am not using ActiveState's Perl all that much these days) and don't want to advertise a site that isn't expecting that traffic... John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747 |
|
From: Randy K. <ra...@th...> - 2006-02-12 22:49:30
|
On Sun, 12 Feb 2006, John Peacock wrote: > Randy Kobes wrote: >> http://cpan.uwinnipeg.ca/dist/Module-Build >> http://cpan.uwinnipeg.ca/dist/Scalar-List-Utils >> http://cpan.uwinnipeg.ca/dist/version > > That's awsome! Can I add this site to the README file as > an alternative source? I wasn't aware of this sites (but > that may be because I am not using ActiveState's Perl all > that much these days) and don't want to advertise a site > that isn't expecting that traffic... That shouldn't be a problem to add this site - feel free. I try to keep the ppm packages in our uwinnipeg repository current, but as it's done manually, they may fall behind. I certainly don't mind a note asking for a current package to be built (there's a link to a form on these pages for doing this). -- best regards, Randy |
Thanks for helping keep SourceForge clean.
X