Re: [PEPr] Comment on Images::GraPHPite

Greg Beaver wrote:

Alan Knowles wrote:

This unfortunatly makes 'pearball' very difficult to implement most software installations I now do, I download a prebuild pear folder and install it into a subdirectory of the application (then add it to the include_path for the app). - This ensures that I dont accidently break client applications when upgrading a global pear install (which even with our BC rules still continues to happen, albeit a little less often..). Regards Alan

Each app should have its own private pear installation anyway (i.e. a custom config file) to take advantage of replacements properly. Then you can set the private pear installation sooner in the include_path. I hope to make this even easier to do when pear actually supports applications in the future. i.e. instead of having to manually create the config, something like: $ pear --application=myapp configure-app /path/to/local/pear

That's nice, but I think Alan was more refering to install of packages where only FTP is available. 98% of all the installation I do for clients are FTP only, with no access to shell... In this case, parameters and package constants are the most flexible to configure the package. -Philippe