# You don't have shell access to the target machine? I have developed code for clients where this was the case and have had to do some fancy footwork to solve the problem

As you have always mentioned you can BEGIN { unshift @INC, "/path/to/Modules"; } on all your scripts and create your own modules directory. If you are talking about modules that need to be compiled you can always cross compile on your machine (statically link the libraries!!!!!!!) and upload them. This can be a royal PITA though. Also remember that running shell escapes (i.e. system and `s) are not always verboten on machines like they should. You can use this to give yourself pseudo-shell access.

Your other points, i.e. making it impossible to figure out enough information from the server or not having compilation tools can make it impossible to install your own modules pretty much means you have to take a hike. Vote with your feet and go somewhere else. Any client who wants a perl solution should usually be more then willing to make a perl solution feasible. If they make it impossible (which is possible) you pretty much have to walk.