NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
current standard (Score:1)
Why is handling testing dependencies best done in the Makefile.PL/Build.PL? What are the advantages over skipping tests?
Re: (Score:1)
I believe that's so that META.yml can express dependencies required for the build properly.
CPANTS penalizes you for not shipping POD checking tests, but their value to anyone but developers is minimal, for example.
Re: (Score:1)
It's not so much "testing" as "checking".
In multi-platform source packages (like CPAN packages) the dependencies of a package require turing-completeness to determine. That is, a dependency on your platform might be different to the dependencies on some other platform.
Part of the job of the Configure phase (Makefile.PL and Build.PL) is to resolve the Complete Dependencies down to a set of Static Dependencies. That static list ca
Module::Build does not work for me (Score:1)
Having a 'make pure_all' and a 'make pure install' (or something similar) is a requirement for me. Is there a way to do that with Module::Build?
You gotta keep the Makefile.PL (Score:1)
Because at the moment, if you install a fresh version of Perl 5.8.8, and then try to install your module, it will fail. Because Module::Build has a configure-time dependency (a dependency needed just to run Build.PL) which CPAN clients are not currently capable of handling.
Go try it.
Until this situation is fixed, and your module is actually installable on the most common stock production Perl versions, you should keep producing Makefile
ExtUtils::MakeMaker will live forever (Score:1)
ExtUtils::MakeMaker will live forever, at least until you can upgrade all those systems with 5.5_003 (Solaris 8) or 5.8.4 (Solaris 10) deployed, or stop caring about the users of "old" versions of Perl. Whatever the goal of the Module::Build authors is, I hope that people will not use Module::Build where they can just as well use EU:MM.