On Fri, May 17, 2002 at 12:21:35AM -0500, Craig A. Berry wrote: > Is this because you are feeding '?' to glob as a wildcard character? On > VMS, '*' means match many characters and '%' means match one character. '?' > has no special wildcard meaning as this example illustrates:
Ok, I've adjusted the test to use sensible things on VMS. > >> t/installed......... > >> Can't cd to (/perl_root/lib/site_perl/VMS_AXP/auto/dbd/sybase/diag/) sybase : no >such file or directory > >> Can't cd to /perl_root/lib/site_perl/VMS_AXP/auto/dbd/sybase/bin../../.. at >/perl_root/lib/File/Find.pm line 535. > >> # Looks like you planned 42 tests but only ran 15. > >> # Looks like your test died just after 15. > > > >This is just never going to work. Too deep. > > Are we intentiolly rooting through site_perl? Hmmm. This is probably the ExtUtils::Installed->new on line 83. It's probably looking at your real packlist. It probably shouldn't be. I've rejiggered it so it doesn't do that, it should work now. sync up from makemaker.org in a few minutes. > >> t/mkbootstrap....... > >> # Failed test (t/mkbootstrap.t at line 87) > >> # '' > >> # doesn't match '(?-xism:Unable to open dasboot\.bs)' > >> # Looks like you failed 1 tests of 18. > > > >Possibly tripping up on the different meaning of -w on VMS. It's expecting > >to be able to write read-only files and uses -w to confirm this. > > It's just that I had too many privs. It's creating a read-only file but > allowing me to create a higher-versioned file of the same name. If I > downgrade privileges it won't let me do that. However, due to a bug that's > only recently been fixed, 5.6.1 will use the account's default privileges > rather than the actual current process privileges when checking with -w, > which could in some cases throw things off for this test. I'd leave it alone. Hmm, ok.
