Here's how I did it -- I took the suggestion from PodMaster and checked out Parse::CPAN::Packages. This is a package that gets the data file 02packages.details.txt.gz .. so I used anonymous ftp to get to CPAN and found the file in /pub/CPAN/modules.

Then I wrote a quick script to do the table lookup ..

#!/usr/bin/perl -w # Which distribution do these modules come from? # # Arguments: # Text file containing data from CPAN # List of modules { my ( $cpanList, $localList ) = @ARGV; my %list; # Load up the CPAN information. open ( CPAN, $cpanList ) or die "Unable to open $cpanList: $!"; # Skip the file header. while(<CPAN>) { next if ( /^\S+:\s+/ ); next if ( /^\s*$/ ); last; } # Load data into a Hash for later retrieval. while(<CPAN>) { my ( $module, undef, $distro ) = split(' ',$_); $distro =~ s#^.+/##; $list{$module} = $distro; } close ( CPAN ); # Look through the list of the modules, outputting which distro # contains that module. open ( LIST, $localList ) or die "Unable to open $localList: $!"; while (<LIST>) { chomp; if ( defined($list{$_} ) ) { printf ( "%30s comes from %s\n", $_, $list{$_} ); } else { print "Not able to find out where $_ came from.\n"; } } close ( LIST ); }
The code works, and it discovered two internal Perl modules that I'd left in, as well as a few Apache sub-modules. The next step is to re-factor that code so that we group together things that came from the same distribution, but that's a refinement that I'll leave till later. Anyway, that answers my original question.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

Update: You can find out about the Apache modules here on the mod_perl web site.


In reply to Re: Finding CPAN modules from module names by talexb
in thread Finding CPAN modules from module names by talexb

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.