I'm just afraid that people will start viewing PEAR as a large
collection of classes in varying stages of development. There is also
the danger of users writing code that references the classes in
PEAR/PHPLIB/, which (as I understand it) will only be their temporary
location.
don't be afraid, that won't happen, I am spending some thoughts on tree structure currently and will post the results (as happend before in "PEAR issues #4") here again
As a side issue (and I've mentioned this before), PEAR really should
have its own source respository. I don't really like the idea of PEAR
being distributed with the PHP releases.
a) the PEAR base classes will be and have to be distributed with PHP (to enable remote install etc.)
b) some of the PEAR classes "may" be distributed with PHP either (should be decided on vote)
c) the rest will go into a separated code repository (eg. on pear.php.net)
andré
--
· André Langhorst t: +49 331 5811560 ·
· andre@php.net m: +49 173 9558736 ·
* PHP Quality Assurance http://qa.php.net *