Hi, Perl Experts. I'm writing some Perl scripts that are for driving the build of some software for my company. The build runs on Windows machines. We have several build machines, and they will all use the same scripts and same Perl modules.
Now, I'm not a Windows person; I'm much more accustomed to UNIX/Solaris/Linux and to having automounted directories for software. I would like to put these Perl scripts and modules on a network drive, and have all the build machines (which I control fully) map the same drive to the location of the libraries. The drive would be laid out as <path-to-perl>/bin and <path-to-perl>/lib. The top script would be invoked as "perl <drive>:\<path-to-perl>\bin\<script-name>", and each top script would unshift "<path-to-perl>/lib" onto @INC. Is that too non-Windows-like? Would it weird out my successor(s) in this job? Another group has a large number of Windows build machines, and they install all their Perl modules in C:\Perl\site, and the Perl scripts themselves in C:\bat. Which means, whenever they change the build software (which is frequently), they have to re-install on lots of machines. What would be the preferred practice here? Please note, the scripts are not at all for end users; they are only for the nightly build system. thanks, --Marilyn -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
