Re: [Module::Build] PPMs for packages built with Module::Build
On Nov 8, 2004, at 2:21 AM, Joshua Hoblitt wrote: On Sun, 7 Nov 2004, Randy Kobes wrote: Until M::B comes into the core, and hence used by ActiveState, what you might consider doing is adding an accompanying Makefile.PL, as Ron mentioned earlier. You Or bundling M::B with Module::Install. Maybe Ken can comment about M::B's current state of core worthy-ness? I think it's ready. There's been some question about whether it needs to do recursive/nested builds before going in the core[1] - my view is that it doesn't. Just because M::B is in the core doesn't mean every core module has to be built with it. Any other opinions? [1] for example: http://sourceforge.net/mailarchive/message.php?msg_id=9957410 -Ken
Re: [Module::Build] PPMs for packages built with Module::Build
On Sun, Nov 07, 2004 at 11:19:11AM -1000, Joshua Hoblitt wrote: It has recently come to my attention that ActiveState does not supply PPMs for CPAN modules that use Module::Build in their build process. I believe you are mistaken. Here's Module::Build itself and another Build.PL based module in their 8xx PPM repository. http://ppm.activestate.com/PPMPackages/zips/8xx-builds-only/Windows/Module-Build-0.25.zip http://ppm.activestate.com/PPMPackages/zips/8xx-builds-only/Windows/Module-Install-0.36.zip Looking at PPM::Make it does appear to have code to handle Build.PL. What probably has happened is the particular modules you depend on are not in ActiveState's PPM repository. This will happen. I have received a support request for one of the CPAN modules that I maintain asking me not to have dependencies on modules that use Module::Build. This places me in an uncomfortable position. Its a little silly as Module::Build based modules should install just fine on Windows, easier than MakeMaker based ones since they don't need make! Its pure Perl (unless there's XS involved). So I'd just recommend to your requestor that they build the dependencies from scratch rather than rely on ActiveState for everything. If there's XS invovled then they should have a chat with ActiveState about it. Its not really your problem. Why has ActiveState decided to isolate their ActivePerl users from a growing fraction of the CPAN? DON'T PANIC! They haven't. They can, however, be a little slow keeping their PPM repository up to date. -- Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/ Death follows me like a wee followey thing. -- Quakeman
Re: [Module::Build] PPMs for packages built with Module::Build
On Sun, 7 Nov 2004, Joshua Hoblitt wrote: On Sun, 7 Nov 2004, Michael G Schwern wrote: On Sun, Nov 07, 2004 at 11:19:11AM -1000, Joshua Hoblitt wrote: It has recently come to my attention that ActiveState does not supply PPMs for CPAN modules that use Module::Build in their build process. [ ... ] There are plenty of modules on the PPM build status page that are built with Module::Build and all of the ones I can identify are listed as failed on all platforms. http://ppm.activestate.com/BuildStatus/ Looking at PPM::Make it does appear to have code to handle Build.PL. PPM::Make isn't used (as far as I know) by ActiveState for building their ppms. What probably has happened is the particular modules you depend on are not in ActiveState's PPM repository. This will happen. I freely admit that I don't use ActivePerl or PPMs. Nor have a done an exhaustive study of the PPMs available. You could be correct. Its a little silly as Module::Build based modules should install just fine on Windows, easier than MakeMaker based ones since they don't need make! Its pure Perl (unless there's XS involved). I agree that it's ironic. :) It is :) What may be the philosoply here is that ActiveState uses an automated build system for their ppms, and for a package to appear on their repository, the distribution itself, as well as all of it's dependencies, must build cleanly and all tests pass, relative to a fresh ActivePerl. Since Module::Build isn't yet in the Perl core, distributions relying solely on M::B to build will fail this test. So I'd just recommend to your requestor that they build the dependencies from scratch rather than rely on ActiveState for everything. If there's XS invovled then they should have a chat with ActiveState about it. Its not really your problem. That's exactly how I feel. Why has ActiveState decided to isolate their ActivePerl users from a growing fraction of the CPAN? DON'T PANIC! They haven't. They can, however, be a little slow keeping their PPM repository up to date. As I stated above all of the Module::Build based modules that I can identify of the build status page are failing. It's not a failure to updated the repository that's at issue here. It's the ability to actually generate the PPMs. Until M::B comes into the core, and hence used by ActiveState, what you might consider doing is adding an accompanying Makefile.PL, as Ron mentioned earlier. You might also ask people who maintain external repositories to add packages not in ActiveState's: http://savage.net.au/Perl.html http://www.bribes.org/perl/ppm/ http://crazyinsomniac.perlmonk.org/perl/ppm/5.8 http://theoryx5.uwinnipeg.ca/ppms/ That's not an ideal solution because, as Ron mentioned, it's fragmented (to help in this, our CPAN search service at http://cpan.uwinnipeg.ca/htdocs/faqs/cpan-search.html returns results of available Win32 ppm packages, including those of some external repositories, and I'm quite willing to add others). -- best regards, randy kobes
Re: [Module::Build] PPMs for packages built with Module::Build
On Sun, Nov 07, 2004 at 10:08:23PM -1000, Joshua Hoblitt wrote: Yes but PPM still has to know how to build it. That's the important part. It obviously can else MB couldn't build itself. Acme::Colour, Data::Page and Module::CPANTS are some other MB based modules which have PPMs. Acme::Colour and Data::Page are both built with ExtUtils::MakeMaker if you call Makefile.PL. I don't have the source for CPANTS handy but I'd guess it's the same. This is true, however... I still suspect that this is due to ActiveState's build environment not having Module:Build available instead of just a problem with CPANrun. I pointed out an example of a PPM failure log which shows CPANrun trying to install Module::Build as a dependency via CPAN.pm and failing due to a missing default. DateTime::Locale is such an example. http://ppm.activestate.com/BuildStatus/5.8-windows/windows-5.8/DateTime-Locale-0.09.txt Again, if you look at the failure log, CPANrun is trying to resolve its dependency on MB but failing due to a problem with the CPAN shell. It would be nice if MB shipped with ActivePerl and would solve the problem but at the moment a fix to the CPAN shell's interactive config would appear to be the simplest and most direct solution. -- Michael G Schwern[EMAIL PROTECTED] http://www.pobox.com/~schwern/ Remember, any tool can be the right tool. -- Red Green
Re: [Module::Build] PPMs for packages built with Module::Build
On Mon, 8 Nov 2004, Yitzchak Scott-Thoennes wrote: Do you know if the source to CPANrun is available? My impression was that it was DateTime::Locale's compatibility Makefile.PL that was firing up CPAN to get Module::Build, not CPANrun doing it. That's sort of truew. Module::Build doesn't invoke CPAN itself. There _is_ an option to generate a Makefile.PL like that using Module::Build::Compat. OTOH, for most users this only has to be done once. I'd list Module::Build as a simple prereq but since prereqs are defined in the build script itself, that can't work. -dave /*=== VegGuide.Org Your guide to all that's veg. ===*/
PPMs for packages built with Module::Build
Dear Sir or Madam, It has recently come to my attention that ActiveState does not supply PPMs for CPAN modules that use Module::Build in their build process. I have received a support request for one of the CPAN modules that I maintain asking me not to have dependencies on modules that use Module::Build. This places me in an uncomfortable position. Why has ActiveState decided to isolate their ActivePerl users from a growing fraction of the CPAN? Is this a technical or business decision? If it's technical, would ActiveState like some help from the Perl community? Will there ever be PPMs for modules that use Module::Build? Why doesn't this issue appear in the ActivePerl bug tracker? Cheers, -J --
