"Sisyphus" <[EMAIL PROTECTED]> writes: > Having followed the same hack as you outlined, I get essentially the same. > However, for me 'dmake test' fails half of its tests - because > t/foo.zip does not get extracted. I expect it doesn't get extracted > because it can't be found - as indicated by the "cannot find either > or .zip" error (which is produced whenever the > Archive::Unzip::Burst::unzip function is run).
I think the path of the zip file, which is passed to _unzip function, gets lost inside of unzip binary, probably due to environment variables inconsistency. > > With both of the Archive::Unzip::Burst test scripts, I fond that the > first 2 tests pass, but the last 2 fail because the blah directory > (which does get created) is empty. Yes, running dmake test is failing when the unzip function is called. This test is called like this: C:\perl5-10\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib\lib', 'blib\arch')" t/*.t But if I call the particular tests like this: perl t\01absolute.t perl t\02relative.t the tests pass. -- Radek
