I'm not actually sure what your question is. CPANPLUS has a facility to send a report of failing tests to CPAN testers and to the author. However modules authors might want "bug reports" sent in a specific way (for instance RT or by direct mail) and they will have indicated this in the README or the POD.
/J\
| [reply] |
| [reply] |
| [reply] |
Er, who is "they"? CPAN RT is graciously provided as a means for module authors to manage "bug reports"¹ or feature requests: for the most part only the registered maintainer of a module will be notified of new tickets and only that maintainer can update the tickets. There is no magic "they" waiting to respond to any and all tickets. However there is no compulsion for the author to use it at all and many will specify the means by which they want to receive reports (this might be by direct mail, via a mailling list, through RT or some other means,) so you should always check in the README or the documentation for a module whether the author has so specified the appropriate channel: not doing so might result in your report being ignored.
/J\
¹ This is quoted because for some modules it seems I get any and all communication through RT.
| [reply] |
If the problem appears to be caused by CPAN, the appearance may be misleading you. CPAN is only a repository, and it's unlikely that the repository itself is at fault. CPAN doesn't create the modules. That's not to say that the module's CPAN installer isn't at fault, but that's not caused by CPAN. If the problem appears to be caused by gcc, the specific module's author or maintainer would probably be interested in knowing about an incompatibility.
But before you assume that the module, the compiler, or the repository are flawed, try to ascertain first whether or not the problem exists between keyboard and chair. Presumably others are already successfully using this module. Did you discover something they didn't? Maybe you did, but before bugging the author, it's best to eliminate your own mistakes as a possible issue. It's often helpful to list specifically what steps you followed, and specifically what went wrong. Then post here explaining how you got the results you did, and asking how you might solve this problem. If you're convinced there's a flaw in the module, post a test case here so that others can confirm it.
If a problem within the module is confirmed, that module's author or maintainer will need to be notified. Authors usually put a "BUGS" section in the POD for their modules explaining where to report bugs.
| [reply] |
