Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96265 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26186 invoked from network); 6 Oct 2016 09:10:06 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2016 09:10:06 -0000 Authentication-Results: pb1.pair.com smtp.mail=remi@fedoraproject.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=remi@fedoraproject.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain fedoraproject.org from 217.70.183.198 cause and error) X-PHP-List-Original-Sender: remi@fedoraproject.org X-Host-Fingerprint: 217.70.183.198 relay6-d.mail.gandi.net Received: from [217.70.183.198] ([217.70.183.198:40816] helo=relay6-d.mail.gandi.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 30/9C-23443-7E416F75 for ; Thu, 06 Oct 2016 05:10:02 -0400 Received: from mfilter41-d.gandi.net (mfilter41-d.gandi.net [217.70.178.173]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id 3B8FEFBA0D for ; Thu, 6 Oct 2016 11:09:56 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter41-d.gandi.net Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter41-d.gandi.net (mfilter41-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id JAIN9iaU1ISN for ; Thu, 6 Oct 2016 11:09:54 +0200 (CEST) X-Originating-IP: 90.109.100.243 Received: from builder.remirepo.net (LFbn-1-6148-243.w90-109.abo.wanadoo.fr [90.109.100.243]) (Authenticated sender: contact@ll-experts.com) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 69BD2FB9EE for ; Thu, 6 Oct 2016 11:09:54 +0200 (CEST) To: internals@lists.php.net References: Message-ID: Date: Thu, 6 Oct 2016 11:09:51 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WdudvUtRgcoaEJIjrsAdDnRcFFXnGStCs" Subject: Re: [PHP-DEV] Intention to move mcrypt to PECL From: remi@fedoraproject.org (Remi Collet) --WdudvUtRgcoaEJIjrsAdDnRcFFXnGStCs Content-Type: multipart/mixed; boundary="Qrcwa3wn4UjKAIKrVfeEfus9O18gAe4bw"; protected-headers="v1" From: Remi Collet To: internals@lists.php.net Message-ID: Subject: Re: [PHP-DEV] Intention to move mcrypt to PECL References: In-Reply-To: --Qrcwa3wn4UjKAIKrVfeEfus9O18gAe4bw Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Le 06/10/2016 =C3=A0 10:45, Pierre Joye a =C3=A9crit : > On Oct 6, 2016 3:41 PM, "Nikita Popov" wrote: >> >> On Thu, Oct 6, 2016 at 5:22 AM, Davey Shafik wrote: >>> >>> On Wed, Oct 5, 2016 at 8:11 PM, Pierre Joye wr= ote: >>> >>>> hi Leigh, >>>> >>>> On Tue, Oct 4, 2016 at 11:58 PM, Leigh wrote: >>>>> Hello list, >>>>> >>>>> It is my intention to create a new PECL package for ext/mcrypt, so >>>>> that it can be removed from master as per the RFC >>>>> (https://wiki.php.net/rfc/mcrypt-viking-funeral) >>>>> >>>>> I do not expect there to be any updates to the extension after it h= as >>>>> been migrated, however we voted to move it there. >>>>> >>>>> Any objections/comments? If not I'll apply for my PECL account in t= he >>>>> next few days. >>>> >>>> I am not sure to follow. >>>> >>>> We rejected to move it out of the core for 7.0. This RFC is about >>>> deprecation for 7.1. >>>> >>>> As much as I want to kill this beast as soon as possible, I do not >>>> think we can kill it in 7.x but 8.x. It is also why I was pushing so= >>>> hard to kill it in 7.0, knowing that this will be tried again and >>>> sadly for 7.x. >>> >>> >>> From the RFC: >>> >>>> In PHP 7.1+1 (be it 7.2 or 8.0), the crypt extension will be moved o= ut > of >>> core and into PECL >>> >>> and >>> >>>> Vote =E2=80=9CYes=E2=80=9D to raise an E_DEPRECATED notice in PHP 7.= 1 when any crypt >>> function is used and to remove the extension from core in 7.1+1. >>> >>> So, per the RFC, moving to PECL in 7.2 is correct. >>> >>> - Davey >> >> >> Furthermore the release process RFC *explicitly* allows moving extensi= ons > to PECL in minor versions. >=20 > I am *not* (I can emphasize text too ;) it is not allowed. >=20 > What I am saying is why we refused to do it in 7.0 and then the same go= all > in for 7.2. That makes no sense to me and it is something we should fig= ure > out for 8 (exts or behaviors). >=20 Checking the https://wiki.php.net/rfc/releaseprocess x.y.z to x.y+1.z (so 7.2) * Extensions support can be ended (moved to pecl) This will not be a major issue, as most people will be able to find this extension in the various binary distribution. This is important to give information about this extension being unsupported, as relying on a dead project. Remi. --Qrcwa3wn4UjKAIKrVfeEfus9O18gAe4bw-- --WdudvUtRgcoaEJIjrsAdDnRcFFXnGStCs Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlf2FN8ACgkQYUppBSnxahi8+QCgvsT9gNWBgPeK0FEpp7u9wZEw acQAnRwde49jxmAx6Xp6BMiHAPpXDmKg =0ZWr -----END PGP SIGNATURE----- --WdudvUtRgcoaEJIjrsAdDnRcFFXnGStCs--