Re: Merging PHPLIB into PEAR

> 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. exactly. PEAR benefits most from being fairly open in the sense that someone comes up with an idea for a library (probably scratching an itch) and contributes it. there are some basic requirements enforced on the code to ensure quality, and that's that. it's available. building an application framework is a great idea. that's why I did it, and am using it. I suggest you join binarycloud-dev if you're interested in an application framework. -alex > -chuck > > -- > Charles Hagenbuch, <chuck@horde.org> > Entropy. It's what's for dinner. > > -- > PHP Extension and Add-on Repository (PEAR) mailing list. > Documentation can be found at http://pear.php.net/doc/pear.html > To unsubscribe, e-mail: php-pear-unsubscribe@lists.php.net from the > mail address you subscribed with. >