CPAN modules that get broken
Some ideas (require further effort):
- the cpXXXan software
- blead breaks cpan emails on p5p
There is the confounding factor in that modules do get fixed, e.g. for hash randomisation.
by visiting CPAN and clicking Testers on broken modules but wonder if someone has scraped that
You can get direct access to the database if you ask, no need for scraping. Try cpan-workers.
I'm fixing broken orphaned modules locally with no way help fix the official and CPAN is in an advanced state of decay.
That's quite selfish, it would be better when everyone benefits from the fix, not just you. You can report the bugs and attach your patch and publish distroprefs into your PAUSE directory. You can email module-authors with your plea for help, often shlomif is glad to comaint modules where the original author is not responsive.
Imagine how fast the 1/2 of CPAN that is probably broken would be fixed!
I think you're overestimating the effect; if a piece of software wasn't urgent to fix without such a list, it won't be any more urgent with one.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
