But then what about the Config.pm file? It appears to have the drive letter where perl is installed hardcoded in. Can I change that drive letter to a UNC path? Or do I not need to mess with it?
-----Original Message-----
From: Shebayev, Eugene [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 8:43 AM
To: 'Declan Mullen'; [EMAIL PROTECTED]
Subject: RE: A perl interpreter that doesn't require registry or PATH sett ings ?

Why don't you simply run perl from a network share? i.e. \\server1\perl\bin\perl.exe
That way you have a single point of administration of all the modules.
-----Original Message-----
From: Declan Mullen [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 22, 2001 6:39 AM
To: [EMAIL PROTECTED]
Subject: A perl interpreter that doesn't require registry or PATH settings ?

Hi,

I need to deploy a windows Perl interpreter to a large number of
NT4/Win2k systems that are owned by other departments within my company.
In order to reduce the objections to this deployment, I need a version
of Perl that does not require the registry or the PATH environment
variable to modified, (explicitly calling the Perl .exe to run scripts
is very acceptable). In addition the interpreter needs to be augmentable
with additional Perl modules. However, I don't need any ActiveX or web
server support.

Many thanks for any recommendations.

BTW I'm a newbie to Perl.

Regards,
Declan

Reply via email to