On 4/9/07, Andreas J. Koenig <[EMAIL PROTECTED]> wrote:
>>>>> On Mon, 9 Apr 2007 15:13:56 -0700, "Joshua ben Jore" <[EMAIL PROTECTED]> 
said:

  > On 4/9/07, Bill Moseley <[EMAIL PROTECTED]> wrote:
  > I'm currently replicating an automated install of Catalyst against a
  > fresh 5.8.8. Interestingly, I saw one interesting failure. Catalyst
  > has oodles of dependencies. At some point during the installation of a
  > sub-sub-sub-* dependency, CPAN.pm deleted its downloaded copy of
  > something it was still in the process of installing. I guess CPAN's
  > build caching mechanism doesn't take into account things in the cache
  > that it still cares about. Ooops!

I could imagine you didn't use CPAN.pm 1.90, right?

For sure. I was testing that a "fresh" 5.8.8 could install it without
error. I use this to help suss out undeclared prerequisites. I have
the same environment for all of 5.6.2/5.8.1->5.8.8/5.9.5 under
non-/threaded, non-/debugging. While I did it manually today, I've got
a harness over it all so I can essentially just request that *all*
those perls attempt to go install a CPAN module of my choice (or a
local distribution) and I get TAP back about which perls passed and
failed.

 # for a single perl and what happened last night
 cd /opt
 rm -rf perl-5.8.8/*
 tar xjf perl-5.8.8.tar.bz2 # a fresh 5.8.8 but with updated CPAN::Config
 /opt/perl-5.8.8/bin/cpan Catalyst < /dev/null

Josh

Reply via email to