Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106689
To: Trevor Rowbotham <trevor.rowbotham@protonmail.com>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <FZ3PBEDob1t-m1TcLhLjyWmEY4VMbZ0LBkx297AVzbtWzuX2y6ZWKRE5Hy4e4Ytx9-VBS6Vr0RpR88jccgfUdktB9c1aNCT0GbxnfvVMAzc=@protonmail.com>
Message-ID: <13a3e8c2-30c1-d0be-2ba6-6541c91581b9@gmx.de>
Date: Thu, 22 Aug 2019 09:28:03 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <FZ3PBEDob1t-m1TcLhLjyWmEY4VMbZ0LBkx297AVzbtWzuX2y6ZWKRE5Hy4e4Ytx9-VBS6Vr0RpR88jccgfUdktB9c1aNCT0GbxnfvVMAzc=@protonmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: PHP 7.2 minimum ICU version
From: cmbecker69@gmx.de ("Christoph M. Becker")

Hi!

On 22.08.2019 at 01:17, Trevor Rowbotham wrote:

> I realize that this may be a little late given that PHP 7.2 initially re=
leased
> roughly 2 years ago, but I came across an issue yesterday regarding the =
minimum
> required version of the ICU library. The user's hosting provider was usi=
ng
> PHP 7.2.1, but it was linked with an ICU version of 4.2.1 (over 10 years=
 old!).
>
> According to the https://wiki.php.net/rfc/deprecate-and-remove-intl_idna=
_variant_2003
> RFC, the INTL_IDNA_VARIANT_2003 constant was deprecated in PHP 7.2. Howe=
ver, this
> RFC did not increase the minimum required version of ICU, which is curre=
ntly
> 4.0 according to https://www.php.net/manual/en/intl.requirements.php. Th=
is
> leaves an opening where PHP 7.2 can be built with an ICU version less th=
an 4.6,
> but the user cannot avoid the deprecation notice because the replacement=
,
> INTL_IDNA_VARIANT_UTS46, wasn't added until ICU 4.6.
>
> Is there any way to increase the minimum required ICU version in PHP 7.2=
 and 7.3 to
> at least 4.6, which would ensure that the upgrade path is actually avail=
able to users
> trying to avoid the deprecation notice?

We usually do not raise any dependency requirements for stable release
branches, to avoid potential BC breaks.  And after all, most of ext/intl
is supposed to work flawlessly with such ancient ICU versions, and to be
able to get rid of this deprecation notice, building with a newer ICU
version is already possible (and, in my opinion, recommendable anyway).

Thanks,
Christoph