|P is for Practical|
First off, you need one person or one committee to decide on what is "standard" for your enterprise.
Second, there are at least two ways to do this that come to mind immediately.
First method would be to set up NFS/AFS/whatever mounts with Perl and its modules all set up. In doing this you could mount it someplace such as /MyCompany/Perl or whatever and provide symbolic links for /usr/bin/perl and friends. This is a "yucky" way of doing it but very similar to what I was doing at a major financial firm back around 2001. AFS was used and we actually had to support multiple versions of Perl on multiple platforms and for multiple OS versions (Solaris vs. SunOS for instance).
The other method that leaps to mind is to build out what you want for Perl from source, add the modules you want and then package this all up and install it everywhere. This is actually my preferred method and in the current environment that I work in we have a standard mount point for all locally produced packages. You can decide if you want to do symbolic linking or just put #!/my/mount/path/perl/bin/perl in all your scripts.
Peter L. Berghold -- Unix Professional
Peter -at- Berghold -dot- Net; AOL IM redcowdawg Yahoo IM: blue_cowdawg
In reply to Re: Ensuring cpan modules installed on all computers in a network are consistent