My first thought is what jellisii2 suggested. On your development system, install PAR::Packer so that you can use its pp utility to bundle your script into a stand-along executable that you can then distribute to others.
Another option is to use App::FatPacker, which you can use to "pack your dependencies onto your script file". I've never use this module, so I can't offer any further guidance about using it.
The only other method that I can think of is to have a Perl installation on a network drive that everyone can access and install your new modules there. Then everyone who can access the network drive should be able to use that Perl installation (with a little work).
To help better understand that last method, here's something that I've done at work that is an implementation of this method. I put a copy of portable Strawberry Perl on a file server. Now anyone on a Windows system that can access the file server can now use this Perl "installation" by running the portableshell.bat file. Now if I install a module into that portable Perl "installation", everyone else using it will also have access to that module.
|