Re: [SVN-MIGRATION] Problems with php-src, PECL-linked extensions, and tagging

There's also the old [idealistic] idea of having every extension live  
in PECL. In this scenario the release manager would take the desired  
stable extensions and package them at release time for the RC then  
test. This idea has been discussed a few times but gets forgotten  
likely due to the large challenges/changes it poses, or if the PHP  
project simply does not want this then we can determine that too. Do  
we want this? What are the pros and cons? I forget most but if this  
idea feels possible then scouring the lists for past discussions will  
be done.

There are a few points which favour an option like #3:
- It's rare to have PECL extensions in core that also do PECL  
releases. Once upon a time a few did, but today it appears only oci8  
does.
- These dead PECL extensions should not be installable. For example,  
'pecl install filter' should never work (although it does today). So  
following this example, having the symlink here lies and pretends pecl/ 
filter is alive.

In other words, today there really is no such thing as an extension  
that is both in PECL and Core so this symlink serves no good purpose  
except maybe to share CVS commit history but thankfully SVN makes  
moving much easier. But maybe Chris has something to say about OCI8  
and why Core+PECL exists for it and works.

Regards,
Philip