Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26869
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 81.169.182.136 cause and error)
Date: Sat, 9 Dec 2006 12:42:09 +0100
Reply-To: Marcus Boerger <helly@php.net>
Message-ID: <1331124224.20061209124209@marcus-boerger.de>
To: Ilia Alshanetsky <ilia@prohost.org>
Cc: PHP internals <internals@lists.php.net>
In-Reply-To: <3B40503A-75F6-41EC-BFCF-56D777501FA5@prohost.org>
References: <3B40503A-75F6-41EC-BFCF-56D777501FA5@prohost.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Moving COM, Socket & mhash to PECL
From: helly@php.net (Marcus Boerger)

Hello Ilia,

  -1 (*), +1, +1, but I think you mean 5.3 as we have released 5.2 already
and I think it is a bad idea to drop in bugfix releases.

(*) If someone takes over i am fine with keeping it. I don't like stuff
nobody takes care of. If we cannot maintain it, it mostlikely has issues.
And those issues might be security related. That is very badfor PHP. Now
saying it works for some or most situations doesn't help a tad bit.

best regards
marcus

Friday, December 8, 2006, 5:03:23 PM, you wrote:

> This is an exploratory e-mail,  so don't panic just yet :-). I am  
> thinking of moving the COM, mhash and socket extensions to PECL in  
> 5.2 and 6.0 releases and was hoping to hear for & against arguments.
> The reason for the making this move are as follows:

> COM:
>         Un-maintained at this time and has a fairly serious number of bugs  
> (26 by latest count, many of which are crashes)
>         Only usable to Win32 users, which I think we all admit are a  
> minority and can always download readily available binaries from  
> pec4win. Since most of them don't compile the extension from source  
> anyway there is IMHO little reason to bundle the sources with every  
> php package.
>         Moving it to PECL will allow for an independent release cycle, which
> may allow for faster fix deployment etc...
>         I hoping the move will encourage people and/or companies to start  
> maintaining the extension.

> mhash:
>         Everything this extension that relies on an external lib to do, is  
> already done by hash extension that is enabled by default and  
> requires no external libs. There is simply no reason to keep it around.

> sockets:
>         Un-maintained.
>         Majority of what it can do can already by done via streams in a much
> more consistent and stable fashion.


> Ilia Alshanetsky




Best regards,
 Marcus