Hi John,
we came across this curious behaviour. Here enclosed please find a
reproducer.
I see the same behaviour -- and also on Perl 5.10.0, so it's not new.
Looks like inappropriate propagation of the last VMS error code.
PS. Why can't a PRODUCT INSTALL of PERL leave an older installation
alone (ie. do not start deleting files in the directory tree), or at
least offer an OPTION to leave the old installation as is?
I'm not sure, but I suspect it's a required by-product of the PCSI
installation process. And somewhat annoying, too!
Using a PCSI kit also has problems if you want to install Perl onto a
cluster-common disk, which is not the boot disk, because you end up with
PRODUCT SHOW PRODUCT listing the kit on one machine but not on the other(s).
The kit itself is just a complete directory tree so perhaps a PRODUCT
EXTRACT command would do the trick instead?
Regards,
Jeremy Begg
+---------------------------------------------------------+
| VSM Software Services Pty. Ltd. |
| http://www.vsm.com.au/ |
|---------------------------------------------------------|
| P.O.Box 402, Walkerville, | E-Mail: jer...@vsm.com.au |
| South Australia 5081 | Phone: +61 8 8221 5188 |
|---------------------------| Mobile: 0414 422 947 |
| A.C.N. 068 409 156 | FAX: +61 8 8221 7199 |
+---------------------------------------------------------+
