On 10/11/07, chromatic <[EMAIL PROTECTED]> wrote:
> Yes, I know. I know *because* I put in that statement on purpose *because*
> the module doesn't work on Perl 5.005.
>
> Is there a better place to put the "Don't bother trying to run this on ancient
> software?" note in such a way that the CPAN testers won't waste their time
> and, eventually, mine too?
Right now, put 'require 5.006' in Makefile.PL and Build.PL.
In Build.PL, you can have
requires => { 'perl' => 5.006 }
Makefile.PL doesn't support that in the PREREQ_PM, but Schwern is
considering a "minimum perl version".
Until I'm convinced otherwise, CPAN::Reporter expects that your
Makefile.PL or Build.PL will flag an invalid platform. Dying in tests
when you didn't check a perl prerequisite up front is just as 'bad' as
dying in tests because you didn't specify a module prerequisite up
front.
Generally, I'd rather see this make its way into metadata so we just
just abort if META.yml says the current perl is too old. Having
things run and die and then having to grep a bunch of output for
various error strings is ugly and fragile.
David
