Re: Merging PHPLIB into PEAR

Rasmus Lerdorf wrote: > > > I hope everyone is happy with this step, at least I am. :-) Why? > > Until now there were two standard repositories one could use and now > > there is the opportunity to join the strengths of both. > > I think this is very good news. This is what the concept of PEAR was > always about. As many have charged, it wasn't an effort to kill other > classes out there, it was simply meant to be a collection point for good > and useful code with some organization and structure applied to it. PEAR did not kill the PHPLib. Kristian (I and my collegues) do not have the time to keep the PHPLib up to date. The current PHPLib CVS needs a big cleanup, the documentation is incomplete and a new version should be out already for months. Of course the NetUSE officals, especially the marketing guy does not like the idea of merging PHPLib into PEAR, but we'll convince them that this step is a must. It started to be a must with PHP 4 / PEAR. Having one central repository is quite important but this does not mean that the repository is very helpful. PEAR lacks solutions for sessions, permissions, authentification, templates... - major topics in the webapplication development. I like most of PEAR, but beside the DB abstraction there're no classes of real importance. This is one reason why PEAR is not that popular as it could be. Let's look forward how we can add the PHPLib to PEAR to build an "application framework" (in the sense as PHPLib is one) that makes PHP 4 even more powerful. Ulf PS: Licence? We'll find a solution. API? We'll see. One way might be to provide some wrapper classes. We'll manage the technical stuff.