Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

Alias (5735)

  (email not shown publicly)

Journal of Alias (5735)

Tuesday May 05, 2009
08:37 PM

April summary - ADAMK::Repository borgs the CPAN

[ #38927 ]

This post is the latest in my series, letting other high-release CPAN authors know about what I'm doing with my repository, in the hopes that they may find something useful and steal the idea for their own repository automation.

I'm going to start doing these as a monthly summary for simplicity.


My rapidly maturing repository automation passed another milestone last month, when I finally managed to integrate the repository model code with both ORDB::CPANUploads and ORDB::CPANTesters.

This is of particular value to the ::Release object, which is now able to tell if and when it was actually uploaded to the CPAN, and what the CPAN Testers results for the release were (mostly of interest if it's the current release).

As I'd hoped, it turned out to be really easy to do the integration.

First, the CPAN Uploads data.

sub upload {
    require ORDB::CPANUploads;
    ORDB::CPANUploads::Uploads->select('where filename = ?', $_[0]->file);

As you can see, I delay loading the class until it's needed, because the model classes auto-inflate at import time. The model name in this case doesn't read very well either, a good argument for naming your tables in the singular.

That code returns a single ORDB::CPANUploads::Uploads object (although the code is really written to return a list) from which I can find out various things.

The main use I'm making of the uploads data right now is to determine which of the modules in my repository that I have released in the past are now maintained by someone else.

This is what that looks like in the ::Distribution model object.

# ORDB::CPANUploads Integration
sub uploads {
    require ORDB::CPANUploads;
    ORDB::CPANUploads::Uploads->select('where dist = ? order by released desc', $_[0]->name);
sub maintainer {
    my @upload = $_[0]->uploads;
    @upload ? lc($upload[0]->author . '') : '';
sub mine {
    $_[0]->maintainer eq ''

The email address stuff there is done because my repository uses emails as usernames (90% of which are emails) so when working with the concept of an author across both CPAN and svn it's simpler to work only in emails.

The other integration of note is with ORDB::CPANTesters, which pulls in the CPAN Testers data. This integration is a hell of a lot heavier, since the only CPAN Testers data export I have access to is around 750meg.

This, ironically, has not just meant resource trouble for me caused by CPAN Testers, but also resource trouble for CPAN Testers caused by me. When a CPAN Testers machine tries to test CPANTS::Weight (the code behind the CPAN Top 100 math) it means that ExtUtils::MakeMaker will load ORDB::CPANTesters to check the version, which results in a 150meg download and 750meg of disk space consumed on the CPAN Testers machine. :)

The result of this rather intensive database pull is that I can easily calculate the PASS/FAIL/etc scores for each of the ::Release model objects.

sub cpan_testers {
    require ORDB::CPANTesters;
    my $rows = ORDB::CPANTesters->selectall_arrayref(
        'SELECT state, COUNT(*) AS count FROM cpanstats WHERE dist = ? and version = ? group by state',
        {}, $_[0]->distname, $_[0]->version,
    my %hash = ( map { uc($_->[0]) => $_->[1] } @$rows );
    delete $hash{CPAN};
    return \%hash;

The main purpose of these extra calls, of course, is as more fodder for my repository analysis reports.

It should now be fairly easy to do things like identifying modules I've given away that I might need to take back by saying.

"Find all the distributions that I've released at some point, which are NOT maintained by me, but which have CPAN Testers failures".

The other new addition to the repository model is Module::Install integration (from an analysis side).

The ::Make role (which provides Makefile.PL/make functionality for repository model elements that control directories which are Makefile.PL-based distributions) now has a set of methods which detect the M:I version used in the Makefile.PL, and the M:I version that was actually included.

At the same time, it also understands which versions of Module::Install are considered "bad" and so allows the generation of a report to monitor modules I have both in development or on the CPAN which need incremental releases to get an updated Module::Install.

D:\cpan\trunk\ADAMK-Repository>adamk report_module_install_versions --sort=2 --bad
Preloading releases...
Preloading distributions...
| Name                 | Makefile.PL | Tarball |
| ORDB-CPANTesters     | 0.86        | 0.85    |
| CGI-Capture          | 0.85        | 0.85    |
| ORDB-CPANTS          | 0.85        | 0.85    |
| ORDB-CPANUploads     | 0.85        | 0.85    |
| ORLite-Mirror        | 0.85        | 0.81    |
| Task-CatInABox       | 0.85        | 0.85    |
| Test-XT              | 0.85        | 0.85    |
| Win32-Env-Path       | 0.85        | 0.85    |
| Win32-File-Object    | 0.85        | 0.85    |
| ADAMK-Repository     | 0.83        | 0.85    |
| Acme-Mom-Yours       | 0.83        | 0.85    |
| Aspect-Library-Trace | 0.83        | 0.85    |
| Class-Inspector      | 0.83        | 0.85    |
| Data-JavaScript-Anon | 0.83        | 0.85    |
| Module-Changes-ADAMK | 0.83        | 0.84    |
| Module-Manifest      | 0.83        | 0.85    |
| ORLite-Migrate       | 0.83        | 0.85    |
| ORLite-Profile       | 0.83        | 0.85    |
| Test-Inline          | 0.83        | 0.84    |
| Test-SubCalls        | 0.83        | 0.85    |
| prefork              | 0.83        | 0.85    |
| PPI-Tester           | 0.77        | 0.36    |
| PPI-XS               | 0.76        | 0.36    |

As you can see, clearly those last two modules with 0.36 are so far out of date as to be somewhat problematic. So last night I cleaned both of them up and did maintenance releases to fix the problem.

The 25 releases that used Matt Trout's problematic first attempt to fix auto_install (which I did a release of before he'd actually finished it) are more of a problem, since I'm getting increasingly bored with doing 5 or 10 releases at a time.

Even though most of the release process itself is automated now, it's still boring and slow(ish) to have to do it 10 or 20 times in a row.

So I think I've finally reached the point where I need to teach ADAMK::Repository how to do an incremental release on it's own.

Getting distribution transforms working (classes which can modify a distribution and prove they didn't break it) and implementing a distribution increment transform is my goal for this month.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.