On 8/21/07, John Mertic <[EMAIL PROTECTED]> wrote: > Added a hack to care of that for 5.2.4. > > I see a few possibilities for a future solution to the problem: > > 1) Include builds from HEAD for only a certain set of known stable > PECL extensions ( APC, uploadprogress, etc ). > > 2) Include builds from HEAD for all PECL extensions that build, but > put those known stable ones in one tree and the unstable in another. > > 3) Include only extensions that have a stable release that builds under win32. > > 4) Include only extensions that have a stable release that builds > under win32 for only a certain set of known stable PECL extensions ( > APC, uploadprogress, etc ). > > 5) Include only extensions that have a stable release that builds > under win32, but put those known stable ones in one tree and the > unstable in another. > > Of these, I see (1) or (2) as the easiest to implement, but (3), (4), > or (5) as being a more ideal solution. Or perhaps there is some > solution in the middle that I'm missing. > > What sounds good to everyone else?
6) Put none and point the users to pecl.php.net and pecl4win.php.net An extension is bundled, available through pecl or both. It is not a joke to fetch extension from pecl42win. We are also working on some improvements on the win32 extension build process (see the ML archive). All in all, I see no reason to bundled a bunch of extensions that we don't support anyway (the php qa/core team). That does not mean they are bot useable or safe, only that we don't support them through php releases. Cheers, --Pierre -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
