in reply to Looking for CPAN.pm insight/best practice

Modules under CPAN are written by volunteers; therefore, while every effort is made to educate those that want to submit something to CPAN that their modules should follow conventions, it obviously does not happen for some.

For those modules you have problems installing in this way, you can make a difference by figuring out why something is failing in your case, and submitting instructions to the module author/maintainer on how to fix the problem. ie. Patches are usually welcomed and tend to get more attention than simply filling out a bug report.

-Scott

  • Comment on Re: Looking for CPAN.pm insight/best practice

Replies are listed 'Best First'.
Re^2: Looking for CPAN.pm insight/best practice
by btr (Novice) on Oct 25, 2005 at 15:55 UTC
    Thanks. I figured that I should somehow let the author know about the problem (after determining that it is a legitimate problem). Thanks for the tip about (not) submitting a bug report.
      I *do* suggest filling out a bug report, especially if you decide not to do anything else; but patches or a detailed "here's what I had to do to fix the problem" report is going to be thousands of times more likely to be utilized to fix the problem than just a bug report.

      -Scott