On 5/21/07, John Peacock <[EMAIL PROTECTED]> wrote:
Austin Schutz wrote: > What is the point of the compatibility file if it requires > Module::Build to work correctly?
FWIW, I ran your module against all of 5.6.2, 5.8.1->5.8.8 in threaded,non-threaded,debug,non-debug perls. All of these perls are 99.9% fresh - the only modification is that I inject a CPAN::Config so CPAN.pm won't require any set up. The only place I didn't get a clean install using a fresh perl was 5.6.2 in all configurations. The failure was in DWHEELER's SVN::Notify and your module wasn't tested. Log transcript is at http://diotalevi.isa-geek.net/~josh/cpan/SVN-Notify-Mirror-0.03602.log.bz2. The purpose of my tests is similar to imacat's. I test that it is possible to take a fresh perl and install a module without failure. When modules require a newer install chain, they have to declare it in their prerequisites. I intended to also test against a current 5.9.5 but my copy is apparently broken right now. I'll share the error just because it is strange and gory but isn't your problem. # CPAN: Storable loaded ok (v2.16) # Going to write /home/josh/.cpan/Metadata # Running make for L/LO/LOCAL/SVN-Notify-Mirror-0.03602.tar.gz # Couldn't opendir : No such file or directory at /opt/perl-5.9.5/lib/5.9.5/CPAN.pm line 3183 CPAN.pm's line 3183: if (! UNIVERSAL::can($obj,$meth)) { Josh
