|Think about Loose Coupling|
Re: Par::Packer, include conf files or not ?by marto (Bishop)
|on Sep 24, 2012 at 09:16 UTC||Need Help??|
" I developped a Perl script on Red Hat Stawberry Perl"
Strawberry Perl is for Microsoft Windows only.
"(I know that this operation will hide the source code but that's also something I'm looking for...)"
"I'd like to deploy this script in various environnements (Windows, Red Hat, Open SUSE, ...) and to do so I did my research and discovered pp (PAR::Packer) that seems to answer my problems."
Just so you're sure, you'll need to create an exe to cover each binary platform On what platforms can I run PAR? On what platforms will the resulting executable run? and more in PAR::FAQ.
"I tried to install Par::Packer from CPAN on my developpment environnement, but the installation failed, so I'm having one major question about Par::Packer that I'd like to be answered"
How did it fail? See How do I post a question effectively?.
"Do I need to include that root-logger.conf in the files that Par::Packer will package (like I'd add a library) or will my module still be able to read it if I leave it "outside" the packaged file ?"
pp see the -a option for adding files. Alternatively have them in a directory you control, however this seems unlikely given the number of environments you want to target.
Update: fixed a couple of typos.