Jeffrey Thalhammer wrote:
David-
Thanks for testing Perl-Critic. This is my first CPAN
module, so I'm not sure what to do about these build
errors. For some testers, CPAN.pm and CPANPLUS.pm
take care of installing the dependencies. But in your
case, it seems like they were not installed. Should I
not assume that testers will install the dependencies?
My plan is/was to have a suite of Perls from 5.6.2 to blead, to
smoketest CPAN uploads. I wanted to have installations as "vanilla" as
possible, in the hope that it would catch omissions and oversights that
a well-loaded developer's box would miss.
But it seems that there is a difficiency in CPANPLUS's prerequisite
tracking that goes haywire with nested prerequisites. Weren't you
talking to imacat about this the other day, or am I getting people confused?
Is MakeMaker sufficient for modules that have
dependencies, or should I be using AutoInstall (or
something else)? What is the "right" way to
distribute a module with several levels of
dependencies? I really appreciate your advice.
To me, MakeMaker seems to be the way to go. AutoInstall is a real pain
for smoke testing, because it actually sits down and stops, waiting for
input on STDIN. Or at least, I haven't sat down and read the docs to see
if there's a way to say "yes" to all manditory modules and "no" to all
optional modules.
Hang in there, we'll get this sorted out somehow. In the meantime, I'm
really sorry about the fails; it makes an ugly blot on the test results
page.
David
--
"It's overkill of course, but you can never have too much overkill."
