Michael Schwern wrote:
!Getting MakeMaker & PREFIX to work on VMS. ! !This is *not* a priority, I don't know if I made that clear. I'm !going to have to hack around this problem for 5.6.1 anyway. I guess I'd like to make clear: binary relocatability of a perl kit @INC et alia is a problem on Unix only. We have no need to support installprefix on VMS since redefining PERL_ROOT (analogous to setenv PERL_ROOT) is all we need to point to a new location. I have often used that mechanism to try out more than one version of perl on VMS. With PERL_ROOT redefined I might be able to run 5.005_03, or 5.6.0 or 5.6.1 or bleedperl. The closest analog on Unix would be building separate kits for different directories then redefining your $PATH (and running rehash) to pick up the version you wanted. Trying to do the analog of the use of installprefix, as documented in INSTALL, on VMS would be a serious waste of time and disk space. Its use should perhaps not be encouraged - at least on VMS, on Unix its another matter and getting the ability to build CPAN extras into an installprefix built perl tree would be quite handy and very much applauded. 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. Peter Prymmer
