Terrific... if you have a Internet connection available. ;-)

I'm starting asking myself why ActiveState have such feature (?) when generating a PPD file from a makefile. It would be more interesting if the documented process worked instead forcing a programmer to look for a solution that solves the problem correctly.

Thanks anyway, I look forward to try and use PPM::Make.

The generated ppd file is coming from Perl tools (ExtUtils::MakeMaker or Module::Build); these make a guess about the package the prerequisites are found in (based on the specified module name), but sometimes the guess is wrong (eg, Win32::OLE is in the libwin32 package, not a Win32-OLE package). Deciding with certainty what package is required requires, ultimately, an internet connection, in order to have access to the CPAN indices where this information resides.

ActiveState, with ppm4, is moving away from specifying package names as prerequisites, and moving to a REQUIRE field, which can specify elements listed in the PROVIDE field (which can be module names). When this gets fully implemented, this problem of needing to map module names to package names will disappear. See this message for details.

The generated ppd file is coming from Perl tools (ExtUtils::MakeMaker or Module::Build); these make a guess about the package the prerequisites are found in (based on the specified module name), but sometimes the guess is wrong (eg, Win32::OLE is in the libwin32 package, not a Win32-OLE package).

This explains a lot. Looks like the same issue that happens with RPM packages on Linux: packagers choose a package name that best fits the requirements.

This would be easier to solve if the PPM is capable to search the available Perl modules inside a PPD package. I would be able, at least, to maintain the dependency list in my PPD file, even if I have to do it manually. I tested all options against Hash-Util, without any results.

Alceu Rodrigues de Freitas Junior
---------------------------------
"You have enemies? Good. That means you've stood up for something, sometime in your life." - Sir Winston Churchill

Thanks anyway, I look forward to try and use PPM::Make.

My take on this is that PPM::Make will enable you to create a ppd file that works - but that ppd file will not contain the <DEPENDENCY> checks for the modules you specified ... and therefore you won't achieve your aim, anyway. PPM just currently doesn't have the capability to perform dependency checks on core and bundled modules - though that may change in the future.

I could be wrong, however - in which case someone will hopefully correct me.

Cheers,
Rob

I'm not sure in what sense you mean "dependency checks"?