Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:2212
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Sun, 8 Jun 2003 01:22:02 +0200 (CEST)
To: Sterling Hughes <sterling@bumblebury.com>
Cc: internals@lists.php.net
In-Reply-To: <1055006122.8243.8.camel@hasele>
Message-ID: <Pine.LNX.4.44.0306080111470.3341-100000@stargate.bhnet.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Moving to PECL
From: edink@proventum.net (Edin Kadribasic)
References: <1055006122.8243.8.camel@hasele>

On 7 Jun 2003, Sterling Hughes wrote:

> Hi,
> 
> So now that the PEAR framework for bundling extensions is in place, I
> figured I'd start a thread about moving all extensions to PECL, and then
> selectively bundling them from PECL (perhaps maintaining physical
> aliases as well.)

-1
I'm strongly against this move. First of all PEAR framework for handling 
extensions is nowhere near complete. It has no support for Windows. It has 
no notion of what version of PECL package can be built with what version 
of PHP. It requires latest and the greatest GNU tools installed on the 
system which is rarely true for some commercial Unixes.

If we are going to bundle most of those extensions anyway, removing them 
to PECL would directly reduce the quality of the release as most of them 
will receive very little testing.

I understand the wish to make the release process more easy, but I'm 
afraid that this proposal will achieve exactly to opposite effect. It will 
certainly make maintenance of the Windows binary releases much more 
difficult.

Edin