|There's more than one way to do things|
Re^2: Par::Packer, include conf files or not ?by HJO (Acolyte)
|on Sep 24, 2012 at 09:51 UTC||Need Help??|
First of all, thanks for your answer, then I appologize for the lack of information of my post or the (now obviously) absurdity that I've said.
"pp won't protect your source code. PAR::FAQ."
I did read this FAQ and I think I didn't express myself correctly, I do not intent to absolutely protect my code from everyone, I know it's simply impossible... What I intend to do is simply deliver a file.exe (on Windows) or a file.sh (on Unix), without the need to install all the modules and add all the libs. The file itself will not be a script.pl, but something a little bit less understandable and of a very simpler use...
"Just so you're sure, you'll need to create an exe to cover each binary platform"
Yes, that's basicaly what I intended to do, I would deliver the file "upon request" to the OS that have been specified
"How did it fail?"
Even if I know that fixing the installation issues I have will also answer my question, I didn't ask on my installation issues, I asked on the behavior of the module itself, so I didn't include a long log of my console when the installation failed (PAR::Packer has a lot a dependencies) to avoid unnecessary informations. If you think this information is necessary to answer me, I'll join it in the next answer
"pp see the -a option for adding files."
I already looked the CPAN presentation of pp (http://search.cpan.org/~rschupp/PAR-Packer-1.013/lib/pp.pm), but my question was intended for developpers which already used pp and knew if the packaged module was still able to read external files or if I had to include them.Regards.