Chromatic wrote:
Maybe the problem is that CPANTS as it exists now measures some metrics better measured on the developer side, not the installer side. It's handy to run the POD coverage tests as the developer of a module, but it's not that interesting for the person installing the module to run them.
Right. But it's interesting for the person who's faced with 4 CPAN modules that purport to do the same thing, and has to decide what order to experiment with them in (esp. important if you're in an environment where installing anything from CPAN involves jumping through a number of hoops).
It would be handy to check that the version numbers and MANIFEST match as the developer, but not really for the person installing the module. A test for forgetting to check in new files to the repository (or add them to the MANIFEST) would be very useful as a developer, but useless to the installer.
I'd hesitate to call them 'useless'. They all act as potential indicators to the module's quality. Of course, we're still finding out what sort of a correlations there is between quality and kwalitee.
N
