Heh -- amusing. But then, if the authors don't change defaults, why would
they bother to run these tests? And I doubt they would ever be "automatic"
in something like Module::Build -- that's not the philosophy, nor do I think
it would ever be a "prereq" for Module::Build. (It could be an addon if
available, the way Module::Build supports "testpod" and "testcover", but
again, you need the users to actually install those modules and run those
actions.)
All-in, this sounds more like another CPANTS criterion. (<ducking ensuing
flame war>)
For personal use, you might also want to see Test::Distribution, which does
some similar sanity checking.
Regards,
David Golden
Robert Rothenberg wrote:
I'm rather annoyed by the spate of CPAN uploads which have defaults from
h2xs or Module::Install that are not edited, things like "Perl extension
for blah blah blah" or "A. U. Thor". In other words, stupid mistakes.
So I've been toying ideas for a module which checks for files which
match regexps of known defaults. Maybe also check that the ChangeLog
has a version which matches the VERSION in the POD (since authors often
forget to update it).
There will be a simple script for authors to run so that it checks for
these things.
I'm actually thinking of calling it something more polite like
"Test::Defaults" but then there is something pleasantly twisted about
encouraging authors to run a script called "amistupid" before uploading
a distribution.
Perhaps a Module::Build utility could run this script before building a
distribution and giving a warning.
Disclaimer: I've made these kinds of stupid mistakes in the past, so
this is not a slight on any particular author or the quality of her/his
work.
Comments/suggestions would be helpful.
