> 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.
I believe ActivePerl will suit all right.
While it's better if it does the registry changes on install it is
NOT required. As long as all the modules are in
..\lib and ..\site\lib relative to perl.exe you don't need to add
anything to the registry. (Or at least you did not when I last time
tried something like this.)
And besides you could automate the registry changes that you would
want to be made. Just use Win32::Registry or Win32::TieRegistry.
Jenda
== [EMAIL PROTECTED] == http://Jenda.Krynicky.cz ==
: What do people think?
What, do people think? :-)
-- Larry Wall in <[EMAIL PROTECTED]>
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
