!That's why we'll hard-wire installprefix to be the same as prefix. Without its !being a configuration option, no one can waste time trying to set it up the !Unix way. But if there is code that wants to look it up in %Config it will !be there. ! !>If getting the VMS to not break !>in the face of a use of installprefix will help you then !>Craig's patch should probably go in. Unfortunately I !>have not had a chance to test it. I am also worried that !>the latest added an interactive question. Remember: they !>can be answered incorrectly. ! ! !The interactive question was for sitebin, which is for "add-on binary !programs," which I assume just means that a CPAN module may need a safe !place to put external executables. Any valid writable directory should work !for that but I've made it default to perl_root:[bin.ARCHNAME] where ARCHNAME !is VMS_VAX, VMS_AXP, or perhaps someday soon VMS_IPF.
I can hardly argue with the approach you've taken in your patch. I have been trying to argue with the notion that applying a Unix (only) "fix" to a VMS non-problem is worthwhile. That is, I have been trying to argue with the notion that without a bunch of junk that unix "needs" (to partially overcome its binary non relocatability) that VMS' config.sh is somehow "broken". The VMS config.sh is clearly not broken - as shown by the argument that you put forth: MakeMaker works on VMS (provided that certain portability concerns are not broken). VMS_IPF eh? Will VMS_x86 or VMS_x86-64 not happen? Peter Prymmer
