On Mon, Aug 10, 2009 at 3:07 PM, David Golden 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
> "
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
Hi,
I am hoping for a bit of help resolving a problem I am having
specifying a requirement to a module using Module::Build and having
that requirement be respected both by cpan and ppm. An example of a
module that triggers my confusion is Text::Wrap, which lives on CPAN
in a package called Text-
