There is a perl script out on the net that will look at all the code that you include in your script and builds a single file out of them all. This one file can then be distributed without any additional files. I strongly doubt it would work on anything that requires actual compiling and linking (like the DBI modules.) While not the best solution to your situation it would make distributing your code easier. You could continue to use the modules of your choice while developing, and just generate the single perl file during your make process.

I think I read about the script in an old perl journal, I'll try looking for it tonight...

Another option, and def not my choice, would be to distribute perl with your code. Users could choose between a full install or expert install. The expert install would let the user use their own perl installation, while the full install would install a base version of perl with only the required modules. This private version would only be used to run your program. This would take a good deal of work for you to setup initially, but would allow you to control exactly what they have. I think that win32 users would be the only ones to accept this, they already do with ActiveState and some nt web servers include their own also.

This also opens up the problem of maintaining several different compiles for several different platforms. Not fun.

The mailman web email script was distributed as a windows file instead of a unix file and was always a pain in the ass to install on our server. Please don't do anything quite that silly.