"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"
It's not required to answer your question, but if you can't install pp how to you expect to use it to develop and test your application in it's packaged form?
"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."
I answered your question, of course a package generated by pp can read files external to it, since you're going to delopy to many servers which you may not have control over, do you think it's wise? Hence my pp -a suggestion. That said, had you a working pp installed you'd be able to test this for yourself.
In reply to Re^3: Par::Packer, include conf files or not ?
by marto
in thread Par::Packer, include conf files or not ?
by HJO
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |