|Keep It Simple, Stupid|
Par::Packer, include conf files or not ?by HJO (Acolyte)
|on Sep 24, 2012 at 09:01 UTC||Need Help??|
HJO has asked for the
wisdom of the Perl Monks concerning the following question:
So here is my situation : I developped a Perl script on Red Hat Stawberry Perl to communicate with an SAP system. 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.
I'd like to create a file that can run on standalone and by standalone I mean : Perl itself does not have to be installed on the destination systems, neither does the modules I'm using (I know that this operation will hide the source code but that's also something I'm looking for...).
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 (I cannot run the tests myself) :
I use Log::Log4perl, and the configuration of my logger is written and loaded from a root-logger.conf file. My question is : 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 ? Or to be clearer : Do I need to include every configuration file related to my script in the files that PAR::Packer will convert ?
I'd also like to ask about your opinion to deploy my script, would you recommend another method to do so ?
Update : I Corrected the case of PAR::Packer