> For now, I see no reason not to make them available (provided that its > not too much effort for Edin to set up the build env on the snaps > machine).
I agree here completely with Wez, I don't see a difference between compiling extensions from php4/ext to compiling pear/PECL extensions on snaps. It's more or less the same deal, except that it's in another directory. The main problem is that there is no infrastructure right now to provide binaries within PEAR/PECL, so there's no pear commandline command to install those packages at all without recompiling. And not everyone has a compiler on Windows nor do they know, how to compile something. I have the possibility to compile some PECL extensions for Windows and put them online for downloading, but I don't see a reason to do that (besides that the windows compiler is not on my box and I have to wait for an opportunity to use it), when we have such a nice infrastructure with the snaps thingy (and the great work of Edin). We don't even have to include them in the offficial release, but maybe just add an additional zip-package with the PECL extensions. And what happens with all those extensions, which are moved from php4/ext to pear/PECL? Are there no windows extension available for them anymore? Or were there never anyway? (I don't know to how many extensions that happened already..) chregu -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
