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
