Eric Wilhelm wrote:
# from Adam Kennedy
Thus, I would like to propose the following.
1. That the running of POD-related tests by end users is considered
harmful.
+20
-40
I don't see that it's harmful at all. It's not even particularly
harmful (merely annoying) for an author to add Test::Pod etc as
pre-requisites. And if you have a religious objection to installing
them, you can always run the rest of the tests for a module, see that it
passes all the functional tests, and force install it.
2. That the test_pod and test_pod_coverage tests by modified ...
I propose that they be deleted.
The build system
There is no "the build system".
> contains all of the needed info to accomplish
the same thing.
./Build testpod
./Build testpodcoverage
$ make testpod
make: *** No rule to make target `testpod'. Stop.
Running a kwalitee check is also part of the pre-release process, but I
omit these 'has a file $foo' metrics because I believe they *hinder*
quality.
I wouldn't go that far, but I don't think they help much.
--
David Cantrell
