Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by bennymack (7469) on 2008.03.19 7:20 (#61706)

    I have also set up a system like this at my $job. I started with the code in CPAN::Mini as an example. I used what I learned to write a CPAN indexer that will maintain a repository of static CPAN modules as well as our custom modules.

    It's worked well so far. I haven't added nearly as much automation to it as the other implementation described in the comments though. I simply add any additional modules that I'd like to mirror to the list and then run an update script that pulls in any modules not present and adds them to the index.

    It's pretty easy for developers to add their modules in. They just run an inject script on their distribution tarball.

    What I like about this approach is that there's no "state", it just works off of a directory of tarballs. The CPAN::Mini method was hard to get right and required doing things in a certain order which eventually drove me to write my own. Plus it only wants to have the latest CPAN version.