|Do you know where your variables are?|
Swallowing up the TARBALL's, as suggested earlier, wont resolve the issue of dependencies. You should also ask why are you going to all this trouble to install the modules like that?
Using PPM install the modules into your development environment.
Create your own modules, when you need them, in a directory under the execution directory. I use /lib. Then at the top of my root executable Perl file you will find:
Then I use ActiveStates PerlApp from the Perl Dev Kit (you could possibly use PAR to do the same thing) to create an exe - making sure I tell it where to find my /lib directory so it can load my modules as well. Generally speaking this will create a bundled file which has all the modules and dependencies in it. This way you need not have Perl installed on the target machines and yet you will have everything you need, including the exact version of Perl you are developing with.
I currently service 1500 users this way with one product. The original version which relied on locally installed Perl and modules was a nightmare - using PAR (which I did for a time ) but more recently PerlApp has been an absolute godsend as far as distribution of executable code is concerned.