# from Christopher H. Laco
# on Sunday 29 July 2007 08:00 am:
>It's rare, but I've been in the situation where
>for some reason (mistmatching dist requirements, failed upgrades, bad
>dist packages, broken troff, etc) the creation of man pages/html from
>the dist pod fails outright.
That reinforces the point that running pod tests on the install side is
a waste of time. Maybe the build tools need to make more noise and/or
refuse to install if pod2man/html goes horribly wrong. After all, we
abort *before testing* if compilation of code fails, so why not treat
compilation of docs the same way?
>But I don't think saying pod tests are something the end user should
>never run is wrong.
So, it would be correct to say that end users should never run pod tests
then? I can totally agree with that. ;-)
>Personally, part of me wants to say: stop worrying about what tests I
>decide to ship and enable with my dists.
I'm thinking the installer should have the option to scan the tests and
skip any that use qr/Test::Pod(?:::Coverage)?/.
Speaking of which, I just noticed that Module::CPANTS::Uses doesn't even
check whether the Test::Pod(::Coverage) modules are used in the *tests*
-- it is happy if they get mentioned anywhere. Further, since
Module::ExtractUse doesn't understand strings, you can simply put this
in one of your tests to game the kwalitee:
my $q = 'use Test::Pod::Coverage; use Test::Pod;';
--Eric
--
"It works better if you plug it in!"
--Sattinger's Law
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
