I hadn't thought about the multiple copies for each installation. That could add up in a hurry.
I agree w/ you 100% about the compiler stuff. We all know there is not a working perl "compiler". I do think we should spread the word that anyone who says they have a compiler is wrong and best, and an out & out liar at worst.
That said, I'm curious to know more about the Perl DevKit from AS. At the info page http://activestate.com/Products/Perl_Dev_Kit/more_information.plex
I see two interesting snippets:
PerlApp (HP-UX, Linux, Solaris, Windows) - Turn your Perl programs into ready-to-run executables. The PerlApp command-line utility binds Perl scripts and required libraries with a binary loader that runs the script. PerlApp can be used to build dependent applications, which require an existing Perl installation on the target computer, or freestanding applications, which will run on a target computer that does not have Perl installed. The Perl Dev Kit includes versions of PerlApp for HP-UX, Linux, Solaris, and Windows.
PerlSvc (Windows) - Convert your Perl programs into Windows services. Build dependent services, which require an existing Perl installation on the target computer, or freestanding services, which will run on a target computer that does not have Perl installed. PerlSvc binds the script with a binary loader; the resultant executables run as a service under Windows NT/2000.
Has anyone used this product to validate either of these claims? I have to admit that it sounds pretty sexy, especially if they build on an AS perl build and will eliminate the duplication of code you mentioned above. And AS has done good things for the perl community in the past so I don't mind giving them my money. Thoughts or experiences anyone?