Christopher Jones wrote: > > > Steph Fox wrote: > >> 1) Distribution woes need to end. With the work Greg's been doing lately >> on PHP_Archive/Phar, that's very close to being attainable now in the >> physical 'getting PECL'd extensions out to people' sense, but unless >> people are running CLI or CGI or have access to their own php.ini they >> still can't do much with those extensions. So we have to seriously >> consider how to recommend extensions to hosts, other than by shipping >> them with the PHP core. > > Steph, Greg > > In interests of clarity for all, can you explain what you anticipate > will change for PECL with Phar/Pyrus for Windows and non-Windows?
That's a great question. I have not written any support yet for pecl in pyrus, as I would like it to be far better. For instance, should pecl4win start building package versions instead of just from CVS, then we could easily install on windows directly from pecl4win. One change that is planned for unix (and not yet implemented) is a concrete build directory, a place where source files are extracted. As you know, currently the pear installer simply extracts to a temporary directory, and builds, then erases the files. This is great when the build succeeds, but when it fails, it makes debugging completely impossible. It also makes patching much more difficult. I have said many times in less formal settings that I expect far more input on how pecl will work with pyrus than we have been getting for the PEAR installer. So, let me say it formally: Pyrus will be far more pecl-friendly, but I will need real input from internals developers to make the thing truly useful. Now that I'm getting better versed in how internals/pecl works, I will also be much better equipped to respond to suggestions than I was a year ago even, so I'm confident we'll get something very nice. Thanks, Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
