On Mon, Sep 1, 2008 at 2:17 PM, chromatic <[EMAIL PROTECTED]> wrote: > Is the CPANAuthorNotes page comprehensive about all of the special magic a > CPAN author has to know to mollify cranky testers? That is, if someone > wonderful wanted to abstract all of the mechanisms away behind a nice, easy > to use, don't make me know about the details interface, would that page take > care of all of them?
It's pretty comprehensive. I can't say that it's exhaustive. For example, I just checked the _downgrade_known_causes subroutine in CPAN/Reporter.pm and saw that it will discard reports if the exit code indicates the exit was caused by a signal. But the wiki has the questions that various CPAN Testers got annoyed answering again and again, so it's probably 90% of the real cases on CPAN. Devel::CheckOS and Devel::CheckLib are the best examples I know of abstracting the mechanism plus they have helper scripts to add necessary files to the "inc" directory and so on. David
