Re: Merging PHPLIB into PEAR

Quoting Paul Meagher <paul@datavore.com>: > I agree with Ulf that the primary audience for PEAR will and should be web > application developers. This would place a requirement on PEAR that it > support the activies of web application developers. This will be difficult > to do it the components are not integrated in some fashion. Once we start > getting into integrating multiple components there is really no escaping > the fact that you are implicitly endorsing an application framework. Once you make PEAR into an application framework, you change the argument from "PHP is great, it comes with PEAR" to either "PHP comes with PEAR, which is what we need" or "PHP has PEAR, but it doesn't do what we need, so PHP really isn't offering us anything". If you are so set on needing an official application framework, then build paf.php.net. -chuck -- Charles Hagenbuch, <chuck@horde.org> Entropy. It's what's for dinner.