Re: Deploying Perl centrally in a Windows-based intranet

I basically have this setup, and it works well. perl lives in a directory on s:. My minicpan lives on \\aliens\cpan\minicpan with CPAN.pm configured to use file://aliens/cpan/minicpan/ as the base directory (and thanks to the LWP magic, this works).

One difference I have is that I have no C compiler installed in the network, and I doubt that MSVC7 can be easily installed on a network share (or rather, I haven't investigated what is necessary for that). I solve that problem by installing the modules into Perl on one central machine, as I am the only Perl developer that mucks with XS modules anyway.

Comment on Re: Deploying Perl centrally in a Windows-based intranet

Replies are listed 'Best First'.
Re^2: Deploying Perl centrally in a Windows-based intranet by spurperl (Priest) on Jun 03, 2005 at 07:19 UTC
Thanks for the rapid reply ! I think you misunderstood my meaning about modules / C compiler - probably I phrased it badly. My users don't install their own modules. I install modules for people to use - so they know nothing about minicpan / cpan - they know that their scripts work. If I send a script to Bob and this script uses the Win32::SerialPort module, this module must be installed where Perl itself is. To install this module, a C compiler is required - only I use the compiler, once per module, to install it. CPAN.pm uses the compiler because the compilation is part of the module's Make process.	[reply]

Replies are listed 'Best First'.

Re^2: Deploying Perl centrally in a Windows-based intranet
by spurperl (Priest) on Jun 03, 2005 at 07:19 UTC

I think you misunderstood my meaning about modules / C compiler - probably I phrased it badly.

My users don't install their own modules. I install modules for people to use - so they know nothing about minicpan / cpan - they know that their scripts work. If I send a script to Bob and this script uses the Win32::SerialPort module, this module must be installed where Perl itself is.

To install this module, a C compiler is required - only I use the compiler, once per module, to install it. CPAN.pm uses the compiler because the compilation is part of the module's Make process.

[reply]