Hi, this is a general reply to what seems to be a theme in this thread. Here are my observations and comments.
It seems to me that a lot of comment from php-dev people is mostly concerned about getting control over PECL. I generally agree that php-dev people have more to do with maintaining the code inside PECL than the pear-dev people. However there are two parts to PEAR (which today still includes PECL): 1) code 2) infrastructure For 1) I think that the php-dev crowd should get really into PECL etc. But for 2) we should work on a joint effort because it simply makes no sense to separate the infrastructure. There is too much overlap and also separating things just makes the user experience worse. Side note: 1) As far as I know this infrastructure does not depend on having PECL in side of pearcvs and in order to make code maintenance easier I think it is very good to move it out of pearcvs. 2) I don't think it's a good idea to let there be too great a difference in features for windows and *nix. I think we the pear-dev people have had to deal with a lot of needless user confusion because of the rift in functionality that was the case in windows and *nix for so long. Therefore I would much rather like to see that we get the windows situation (especially in regards to binary distributing) worked out along with the *nix. Of course we can't magically make compilers appear on the windows user machines but binary distribution should be sufficient. So while it is true that moving things to PECL will only gain *nix folks something and will not take away from the windows crowd it does create a rift that will create needless confusion imho. Regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
