Chuck Lane wrote:

> I don't think so; checking the DESCRIP.MMS:
> 
>     install : $(MINIPERL_EXE)
>         @ @perl_setup.com
>         If F$TrnLnm("Sys") .nes. "" Then Deass SYS
>         $(MINIPERL) installperl
> 
> So even if you play around with definitions of PERL_ROOT earlier, the
> execution of perl_setup.com will set them back to their "install"
> values. (And I guess I just answered my own complaint as to why
> perl_setup.com doesn't set PERL_ROOT in a self-relative way)

Configure.com still allows you to type in virtually any response to the
"where do you want your PERL_ROOT?" question.  So I might still add 
device mount checks, writability, etc. to the user response.

I've mentioned this before but perhaps it bears repeating that the way 
that I use perl_setup.com is to do this:

  $ create/dir SYS$COMMON:[PERL]  ! if box never had perl before
  $ copy perl_setup.com SYS$COMMON:[PERL]
  $ set file/protection=(w:re) SYS$COMMON:[PERL]perl_setup.com

then if I want to switch versions or installation disks I'll simply
edit the PERL_ROOT DEFINE statement in SYS$COMMON:[PERL]perl_setup.com.

This process is still not automated :-{

Peter Prymmer

Reply via email to