in reply to ActiveState modules

You should be aware that ActiveState's method for "choosing" moules goes something like this:

  1. Mirror the CPAN
  2. Run each module through an automated compile
  3. If it works, it gets put on ASPN (which is what the PPM tool accesses)
So, be warned that this is something that didn't pass an automated build process; that may be for some simple and easy-to-fix reason, but it might be a huge headache as well.

Also, note that searching for module names with the familiar '::' separator doesn't always work with PPM. Try replacing it with '-'. I found that the build failed for this module by visiting the PPM site's "G" section (Must... resist... calling it... G spot...) and searching for 'Graph-Layout-Aesthetic'.

radiantmatrix
require General::Disclaimer;
s//2fde04abe76c036c9074586c1/; while(m/(.)/g){print substr(' ,JPacehklnorstu',hex($1),1)}

Replies are listed 'Best First'.
Re^2: ActiveState modules
by thekestrel (Friar) on Mar 03, 2005 at 07:30 UTC
    RadiantMatrix,
    Thats pretty neat. I didn't realize they autotested from CPAN. At least I know they tried now so I can pull the package apart and see what is broken for windows.
    Regards Paul.