Re: Moving to PECL

php.internals

Frank M. Kromann

23 years ago
I agree with Edin here. We need to make sure the Windows builds are not too far behind the *nix releases. In other words we need to make sure everyting is in place to build and release on Win32 before we move all extensions. - Frank
> 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