Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:79004
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <20141119143329.GX2294@phcomp.co.uk>
References: <CAFMT4NpJxuuqc-wTr1aE4K+wZBT8+04j+9-SsY+nhUMU83fDUg@mail.gmail.com>
	<546C9E22.6090301@fedoraproject.org>
	<20141119134632.GV2294@phcomp.co.uk>
	<546CA8C0.1060707@gmail.com>
	<20141119143329.GX2294@phcomp.co.uk>
Date: Wed, 19 Nov 2014 17:37:12 +0100
Message-ID: <CAH-PCH5xcSrQ1Kb+j8oATK0K0pVmT6rbADXNGo_+ytM_xSeAqQ@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a113dff6ed9c429050838d234
Subject: Re: [PHP-DEV] [RFC] Remove PHP 4 Constructors
From: tyra3l@gmail.com (Ferenc Kovacs)

--001a113dff6ed9c429050838d234
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 19, 2014 at 3:33 PM, Alain Williams <addw@phcomp.co.uk> wrote:

> On Wed, Nov 19, 2014 at 02:27:12PM +0000, Rowan Collins wrote:
>
> > PEAR is not a single organisation who can mass update all the
> > modules; the guidelines could be updated, if they haven't been
> > already, but there would still be a whole repository full of
> > libraries which used this.
> >
> > Now, whether that's acceptable or not, I don't know, but it does
> > highlight the size of the compatibility break.
>
> How many servers are stuck on PHP 4 ?
>
> Of those 'stuck' servers, how many have applications still under active
> development ?
>
> The point is: how many people would get annoyed if PEAR stopped supportin=
g
> PHP 4 ?
>
> IMHO: making PHP 5.3+ the PEAR baseline would not seem unreasonable.
>
>
There were already discussion about bumping the php requirements for the
next PEAR package:
http://comments.gmane.org/gmane.comp.php.pear.devel/50823
But what it is more important is that even if some PEAR packages will be
getting new releases with modern/refactored APIs with bumped major
versions, that will still not break the already existing installation, and
people will still be able to install the latest package version which
supports their php version (and it would be still possible to continue
releasing patch versions for security updates for the php4 compatible
versions).
So while I agree that PEAR in it's current form will be the biggest public
repository with code affected by this change, it isn't like they can't move
forward or that users using PEAR for their projects will be left without an
upgrade path and plenty of time to execute it.

--=20
Ferenc Kov=C3=A1cs
@Tyr43l - http://tyrael.hu

--001a113dff6ed9c429050838d234--