Re: requirements and the ppd action

On Mon, Aug 10, 2009 at 3:07 PM, David Golden<[email protected]> wrote:
> Unfortunately, the way Module::Build::PPMMaker is implemented, you
> have to fix it afterwards.
>
> To do this correctly, Module::Build::PPMMaker would need to access the
> CPAN index files that map module names to distribution names.  (the
> "02packages.details.txt.gz" file in the "modules/" directory of a CPAN
> mirror).  Or it would need to use an installed & configured CPAN.pm or
> CPANPLUS to do the same.
>
> Even that is difficult to get exactly right, since that index only
> lists the *latest* version of modules and distributions.  So to find
> where an arbitrary module came from, you need an index of BackPAN, and
> those aren't easily available.  I believe Adam Kennedy was working on
> making one available through CPAN, but I'm not sure how well
> documented it is.
>
> All of this is to say: the easiest thing is to fix it up afterwards,
> unless you're feeling motivated to fix the problem once and for all
> for everyone.
>

In cases where the latest version of modules and distributions will
suffice, you can also use PPM::Make:
     http://search.cpan.org/~rkobes/PPM-Make-0.96/
which uses a web service and/or a local copy of the CPAN.pm indices to
associate the module name to the CPAN distribution.

-- 
best regards,
Randy