Re: [PEPr] Comment on Images::GraPHPite

On Wed, 2004-09-01 at 21:13, Philippe Jausions wrote: > 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. I actually think this would help you maintain a local copy for X app on ya machine, like say I have app1 and app2, I want to update all pear stuff in app1, so I do something similar to what Greg said, all is updated locally on my machine (or my development server or how ever other people here work) and THEN I upload the updated folder to my clients ftp ... At least this is how I look at this thing :) -- Regards Helgi