The Problem:
PECL extensions in core are often not synchronized making it
difficult to document or determine what is available.
Possible Solutions:
A) Have independent releases for PECL extensions, then include some
in core during the RC phase
B) Use the Zip extension as a test case and figure out a way to
ensure that synchronization happens
C) Leave as is, but officially remove them from PECL. And add
warnings/info in both pecl.php.net/ and php.net/manual/
D) In addition to any of the above, allow 'pecl install foo-cvs-head'
or similar
E) ?
Before any of this we must ask ourselves "What is PECL?" because the
answer to this question seems to change often and differ for
everyone. And let's write down what we decide and finally make it
official. No exceptions. And please no jokes about Siberia.
Examples that show what is Broken:
json, filter, pdo, hash, sqlite, ...
PECL versus Core:
There are rumors that once an extension is included into core that
the PECL release cycle dies with it. This is not an official rule
(that I can find) but it happens a lot. So what this means:
- Bug system: No longer can we tell which are fixed in PECL and/or
Core, or know where to report them - Website: It's wrong since there are no new releases or changelogs
posted - PECL: Can't be trusted, how are we to know what is true? How to
install with older versions of PHP? - Docs: Are wrong as they refer to this bogus information and suggest
'pecl install foo'
Please think about this problem and overall doable solutions and
please do not focus on individual people or packages because the
above are only examples of this wide-spread problem. I write this
email because there is a problem but I fear not everyone is fully
aware of it, and it needs to be solved (and documented) once and for
all. Thoughts?
Regards,
Philip