Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • If your TPC is 1.04 or prior, upgrade it first to the latest version and it would be less harmful. The same thing can be said for every Test:: modules concerned.

    Besides, skipping pod coverage test with environmental variables (TEST_POD or AUTHOR or anything) is not a good idea, as it tends to be ignored even by module authors (especially those who copy the test from someone else's modules, and thus, don't know it should be enabled somehow). Actually there're modules that have pod coverage test that fail if you enable TEST_POD. Pod coverage test should guarantee the modules' kwalitee. I don't want it to deceive us, even unintentionally.
    • I have no problem upgrading my own installation to the latest stuff. It's my own dev stuff, y'know? What I'm testing now is that a plain, fresh, ordinary perl can still install stuff. If modules are going to require testing infrastructure that doesn't work properly until a high enough version then modules are going to have to include those "high enough" versions in their PREREQ_PM lists.

      Without proper PREREQ_PM, modules just fail to install and that sucks.