| [reply] |
Thanx for giving it a review, dolmen. Any takers for my
naming/category issue :)?
I've updated my local Build.PL's build_requires (=>0,), thanx for the tip.
(and yes, the amount of test green also surprised me)
As for the tests, I might go from really very light to just fairly light, but a realistic portable testset to be run from CPAN.pm just doesn't seem quite realistic to me:
Portability for some of waitconds functionality like iostat (diskidle) is one problem, writing a portable test for that is another, quite worse one. Plus the 30 second delay required to get something at least somewhat sane out of iostat...
Btw1, is there some Perl standard distribution location for
such extra stuff, to get it installed in the filesystem, but out of
the way? Other than say just occupying /usr/local/share/doc/waitcond_cpan_distribution? (and anything /usr requires being root or a sudo prefix in the CPAN.pm config, something I'm also not that happy about)
q2, is there a way to add cygwin (but not pure windows) as an os for the cpan testers?
q3, my current understanding is that the tests may be automated, but the report may also be manually augmented(?) to contain some additional information and comments. Are such augmented/more valuable reports marked or filterable in some way? Or do I have to hope for the tester to fail the test, or add an email so I at least won't miss his comments/reviews?
| [reply] |