Re: Distribution of PEAR w/ progs.

Markus, I totally understand where you are coming from. I guess what boggles me is, isn't PEAR supposed to be a common Library that PHP developers can use? Common libraries aren't supposed to be distributed. I see though your point, and totally agree. - Stan Markus Wolff wrote:

Stan Lemon wrote:

When you guys/gals create a prog that uses PEAR and distribute it, do you include your PEAR packages with it? I know that's not supposed to be the way it works, but I'm finding that at least my three web hosts don't know how to properly install & configure PEAR. What do you do generally?

Actually, bundling the used PEAR packages *is* the better way to go if you want do distribute your app. Imagine for example you use a package called PEAR_DamnNiftyPackage in version 1.0, which your host has installed. You deploy your app and everything´s fine. A few weeks later, your host upgrades to DamnNiftyPackage 2.0, which has a completely revamped API with tons of new features... at the cost of backwards compatibility. Unfortunately, your host didn´t post any warnings about that change. Even more unfortunately, the website that generated a $1.000.000 revenue per day for your customer is now broken, because your app doesn´t cope with DamnNiftyPackage 2.0 ... now your customer is a little upset.... You get the picture? ;-) Regards, Markus