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

What's the problem here? On my box, I run hundreds of programs who use hundreds of libraries and modules, all written by a cast of thousands. None had shell access to my machine. That's why software comes with a setup procedure. Whether it's called ./configure; make; make install, setup.exe or packageadd.

You lack compiler tools for the target machine? Case in point: I was developing code for the client I just intimated to above and his target machine was a Win2K box. I run strictly Linux on my development system and do not have access to Microsoft compilers.

Well, that's your problem. And a serious one. Even if you were to write 100% pure Perl, it means you roll out software that you haven't tested on the target platform. Remind to never do business with you.

Uncooperative hosting facility.

Then take your money elsewhere.

I don't see that Perl or CPAN needs to solve any of the problems you mention.

Abigail