Show quoted text> hmmm.... what would you suggest? I have many modules that have
> dependencies and I run into this situation when using other peoples
> modules as well. I did an install of a module yesterday that had 4
> dependencies, each of those combined had another dozen dependencies,
> it took a couple of hours to get it all done, so I see your point. I
> just don't have a good solution.
>
> Michael
It's expected that a module may have prereqs
but typically the cpan* installers can resolve them automatically. I
recall previously finding dists that use their own modules during
Makefile.PL (and therefore attempt to use prereqs before being able to
declare them), though if you said you had (found others out there like
this) I'd certainly believe it.
It just now occurred to me that this is what the 'configure_requires'
key is for in the CPAN::Meta file.
Applying the attached patch works for me.
According to the CPAN.pm change log it should work starting with cpan
1.91_51 which is from 2007-07-07 (stable 1.92 as of 2007-09-15).
The patch upgrades the META.yml to version 1.4 of the spec (where
configure_requires was introduced) and adds File::SafeDO in
'configure_requires'. Prereqs listed there are attempted to be resolved
before running Makefile.PL.