Re: Something about PEAR policy

Björn Schotte <bjoern@baer.main.de> wrote: > there's a new discussion about migrating PHPLIB's > classes into PEAR. As Nathan Ruby says in his e-mail, > you PEAR folks don't want to have more than one class > for each category, e.g. two or more classes for DB > abstraction, templates and so on. > > Is that true? not really. (okay, a few people might think that way, but they'll eventually come to realize how wrong they are. :) the real problem to integrating things like phplib or binarycloud or other templating systems into pear, in general, is that right now it requires it be maintained in the pear cvs tree. this is where pear is still very un-cpan-like. that is the biggest boulder in pear's path right now. i know stig has done some work in defining a package format for bundling pear contributions, but there's only been limited progress on the actual infrastructure for uploading and releasing those components through pear.php.net. when that project finally gains some traction, i suspect we'll see an explosion of useful contributions to pear. jim