Dan Sugalski wrote:
> >Exactly our current problem decision. We are installing new bigger
> >disks shortly, so I'm going to test with perl_root in my tree, and
> >when we get the new drives installed, change descrip.mms and install
> >on a production disk.
>
> If you did an MMS INSTALL into your home directory (or anywhere, really)
> you don't need to reinstall the thing to move it to a different disk. Just
> do a BACKUP of the tree from where it is to where it should be and you'll
> be fine.
This too is true (and good advice). What I do when I install perl is:
$ create/dir sys$common:[perl]
$ copy perl_setup.com sys$common:[perl]
$ set file/prot=(w:re) sys$common:[perl]perl_setup.com
Then if I need to move my perl installation to another device I do (this is
from memory and the backup command may not be quite correct):
$ backup dka100:[perl-5_6_0...] dka300:[000000...]
and I edit the sys$common:[perl]perl_setup.com so that instead of this:
$ define/translation=concealed Perl_Root DKA100:[PERL-5_6_0.]
it reads:
$ define/translation=concealed Perl_Root DKA300:[PERL-5_6_0.]
that is, perl on vms is binary relocatable (it also is on Windows and Macs,
but not unix).
Hope that helps.
Peter Prymmer
