view release on metacpan or  search on metacpan

README  view on Meta::CPAN

DESCRIPTION
    CPAN testers provide a valuable service. The reports are available on
    the Web - for example, for CPAN ID "MARCEL", the reports are at
    <http://cpantesters.perl.org/author/MARCEL.html>. I don't like to read
    them in the browser and click on each individual failure report. I also
    don't look at the success reports. I'd rather download the failure
    reports and read them in my favorite editor, vim. I want to be able to
    run this program repeatedly and only download new failure reports, as
    well as delete old ones that no longer appear in the master list -
    probably because a new version of the distribution in question was
    uploaded.

    If you are in the same position, then this program might be for you.

    You need to pass a base directory using the "--dir" options. For each
    distribution for which there are failure reports, a directory is
    created. Each failure report is stored in a file within that
    subdirectory. The HTML is converted to plain text. For example, at one
    point in time, I ran the program using:

        sync_cpantesters -a MARCEL -d reports

lib/App/sync_cpantesters.pm  view on Meta::CPAN

CPAN testers provide a valuable service. The reports are available
on the Web - for example, for CPAN ID C<MARCEL>, the reports are at
L<http://cpantesters.perl.org/author/MARCEL.html>. I don't like to
read them in the browser and click on each individual failure report.
I also don't look at the success reports. I'd rather download the
failure reports and read them in my favorite editor, vim. I want to
be able to run this program repeatedly and only download new failure
reports, as well as delete old ones that no longer appear in the
master list - probably because a new version of the distribution in
question was uploaded.

If you are in the same position, then this program might be for you.

You need to pass a base directory using the C<--dir> options. For
each distribution for which there are failure reports, a directory
is created. Each failure report is stored in a file within that
subdirectory. The HTML is converted to plain text. For example, at one
point in time, I ran the program using:

    sync_cpantesters -a MARCEL -d reports