Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:82392
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.43 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
References: <bc6d032454578020cdd2cef172698534.squirrel@webmail.klapt.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <bc6d032454578020cdd2cef172698534.squirrel@webmail.klapt.com>
Message-ID: <80E6AA15-23FA-4A77-B50E-6819120E7B58@gmail.com>
Date: Wed, 11 Feb 2015 08:38:02 +1100
Cc: "internals@lists.php.net" <internals@lists.php.net>
To: Anatol Belski <anatol.php@belski.net>
Subject: Re: [PHP-DEV] [RFC][VOTE][RESULT] Removal of dead or not yet PHP7 ported SAPIs and extensions
From: davidkmuir@gmail.com (David Muir)


> On 10 Feb 2015, at 9:29 am, "Anatol Belski" <anatol.php@belski.net> wrote:=

>=20
> Hi,
>=20
> the voting on the removals in PHP7 in hereby finished. The results are
>=20
>=20
> item                   yes:no
>=20
> sapi/aolserver         32:0
> sapi/apache            32:0
> sapi/apache_hooks      31:0
> sapi/apache2filter     23:1
> sapi/caudium           30:0
> sapi/continuity        28:0
> sapi/isapi             28:0
> sapi/milter            10:9
> sapi/phttpd            26:0
> sapi/pi3web            24:0
> sapi/roxen             23:0
> sapi/thttpd            25:0
> sapi/tux               25:0
> sapi/webjames          25:0
> ext/imap               14:19
> ext/mcrypt             15:18
> ext/mssql              17:13
> ext/pdo_dblib          4:18
> ext/sybase_ct          17:1
>=20
> As most of the items are considered to be removed, the ones to stay
> untouched by the 50%+1 requirement are
>=20
> ext/imap
> ext/mcrypt
> ext/pdo_dblib
>=20
> I'm going to implement and tag the changes considered ASAP. Regarding the
> stuff to considered to be removed from the core - if there are some
> supporters, the sources will be made available in the git tag. They can be=

> anytime ported to PHP7 and possibly resurrected.
>=20
> Regards
>=20
> Anatol
>=20
>=20
>=20
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20

Does this mean PHP will be taking on the role of maintaining libmcrypt as we=
ll? If a security issue is found, what is the course of action?

Cheers,
David

Sent from my iPhone=