I just wanted to get some guidence from the monks on the placement of perl modules, standard and home grown. I maintain perl on just a couple of machines and I do most of the coding in the unit myself. I currently have the standard modules installed on each workstations C: drive (WinXP, ActiveState 5.6.1). I also have a general home grown module library contained on a network drive. I add the lib to the path at the start of those programs that need it. I have it set up this way to keep from having to push the changes to these libraries to each individual machine. They are in active development and change frequently.
The set up seems a little kludgy to me in that, whenever I add modules to my own workstation during development, I have to remember to go to each workstation and load those modules to it. Too often I forget, or miss one. How embarrasing
I have, occasionally, considered moving the entire Perl library out to a network drive so that I could update once for everyone. However, it seems the windows setup wants to be installed on the local machine and I am unsure as to how difficult it would be to change things.
Has anyone had any experience trying this on a Win32 platform?
Thanks for the great suggestions. It seems like one or more of them will meet my needs. Thanks again.
use strict; use warnings; use diagnostics;