Michael Schwern wrote in a response to me:
!> lib/ExtUtils/t/00setup_dummy.........ok
!> lib/ExtUtils/t/backwards.............ok
!
!If you already got the ok from backwards.t then its not hanging there but
!the next test, basic.t.
Indeed.
!> I note also that this patch does not address the problems
!> that perlivp is having with ExtUtils::Installed on VMS
!> (which I suspect is a problem confined to Installed.pm).
!
!What problems are these? Is this about running VMS with a case-sensitive
!file system again?
I suspect not. In a run with a modified perlivp.com from an installation
of 5.8.1@ I see this:
$ perlivp -v -p
<snip>
## Module `VMS/DCLsym' appears to be installed.
## Module `VMS/Stdio' appears to be installed.
## Unnecessary module `bLuRfle' does not appear to be installed.
ok 5
## Checking installations of later additional extensions.
# ::perl_root::lib::VMS_AXP::5_8_1::.packlist; NO VERSION
## Perl; 5_8_1
## dbd::mysql; 2.1027
## dbi; 1.37
not ok 6
It appears that perlivp is trying to locate a
::perl_root::lib::VMS_AXP::5_8_1::.packlist
file. It should be trying to locate either a
perl_root:[lib.VMS_AXP.5_8_1].packlist
file or a /perl_root/lib/VMS_AXP/5_8_1/.packlist file. That former file
spec
is OK as far as the DCL DIRECTORY command in concerned:
$ dir perl_root:[lib.VMS_AXP.5_8_1].packlist
Directory PERL_ROOT:[LIB.VMS_AXP.5_8_1]
.PACKLIST;1 142 3-APR-2003 13:53:07.41
Total of 1 file, 142 blocks.
But in fact it appears to not have a VERSION in it:
$ search perl_root:[lib.VMS_AXP.5_8_1].packlist VERSION
******************************
PERL_ROOT:[LIB.VMS_AXP.5_8_1].PACKLIST;1
/perl_root/lib/unicore/version. type=file
So perhaps perlivp does need modification(?) so as to skip
the VERSION check for a .packlist file.
Peter Prymmer