PS. I don't believe compiling perl source code is a good Idea if you are distributing to consumers though!
Since it's compiled and it fancies the machine it was compiled on, moving it means having to ensure that the staticly linked libaries are all in the same places on the users machice as they were on the machine the code was compiled. I just happen to be in the unique position of distributing a product that I'm able to choose any operating system I want, any software I want, and configure it in any way I want. So I decided to secure it with perlcc was the best way only because the code would never be moved onto a server other than the one's we are distributing. And even if someone slaved the hard drive and retrieved the perl compiled programs, it would be impossible to run on another machine with how proprietary I made it to the servers we build. Tony -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
