Re: [PEPr] Comment on Images::GraPHPite

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 which would create the configuration file in /path/to/local/pear/.config and put the php_dir etc. as subdirectories of /path/to/local/pear and this would allow $ pear upgrade --application=myapp DB which would automagically grab the config from /path/to/local/pear/.config as if you had done $ pear -c /path/to/local/pear/.config upgrade DB doesn't have to be exactly like this, but certainly something like it would help a lot. Greg