Re: Ajax PEAR package

Sergio Carvalho wrote:

Matthew Fonda wrote:

This is a problem without solution. Because of the no-overlap rule in package acceptance, there is no way PEAR can guarantee it contains the best implementations for any given package. Packages are evaluated once and only once, at acceptance time. This is so clearly wrong I can't understand how the no-overlap rule is so widely accepted. While I do understand the reasoning behind disallowing two packages for the same purpose, I am of the opinion this is a serious PEAR flaw. This effectively removes competition, which is one of the primary forces behind OSS quality.

We sometimes do deprecate old packages, like phpdoc. Generally the aim is to make the packages that get accepted fairly well designed and flexible, which usually allows interal refactoring to improve the code. Furthermore the no overlapping code is not triggered when something tries to achieve the same thing with a new approach, that approach can be smaller footprint (see Cache_Lite) or with a broader scope (see MDB/MDB2). Anyways .. I dont see the problem. Play with it or not. If you need motivation about PEAR and its success look at the stats page and realize we were below 10 million earlier this year: http://pear.php.net/package-stats.php regards, Lukas