Newsgroups: php.internals,php.pecl.dev Path: news.php.net Xref: news.php.net php.internals:96259 php.pecl.dev:14014 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 2491 invoked from network); 6 Oct 2016 03:11:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2016 03:11:07 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.41 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.213.41 mail-vk0-f41.google.com Received: from [209.85.213.41] ([209.85.213.41:33243] helo=mail-vk0-f41.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C6/69-23443-AC0C5F75 for ; Wed, 05 Oct 2016 23:11:06 -0400 Received: by mail-vk0-f41.google.com with SMTP id z126so6300623vkd.0; Wed, 05 Oct 2016 20:11:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gJwodpxvEc8q1GfUYLv1bBy1oYbDFrhjadN70fm1d1E=; b=BRpTj3CLzmAwBvj1oXoSDkLqFSv1BPHc+uinwd52QEOrTpo0TEOv9n5VxXGMQm4Owo ENM5sF7R/ZSA0nusEPngohjjB+wtNmKjILjjNShBSOjPqidvFBXY/C8tIuJplIDhoAgQ ZtM3ujN1LXRAyx7Q4FWO7XM+0YhcQMqEDbGMNxDeT7+ckhLrTKAg/hkWR0Og5+HuCal2 ihGwwMi4wEKXwniEKBK/ezxsiVENqvc2FvB05qBRIwKE9OwoCDAXoq7rq1otQndOgYrI 9djqrobd3TFzr4pPPZ9RtualMEGESOFYbCZX20rGpeNJpVdueh3i5EtslTFmUfkq4gb7 ts8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gJwodpxvEc8q1GfUYLv1bBy1oYbDFrhjadN70fm1d1E=; b=f3HFIv1PUtAMWuaj34cwzJTEjBcYS0buqqHxeWE09EdWDm+ucKf7rbsb/2KZgS4KjL ABL9+kaRW5K2g+CmwdIplAb+e+aO8RM5EAhMUZ18R9csvxkuujwa+1QlNRw0kBW77bJz +OzbuJ8PJBjjPvstp/Q3SfLlv5AOzVvqXzKBu+RpGVq5LHNVFKyg3lO/OWW8cENsP89t FeZkECTqfRiw/5Phe2u9Krn12ARcxGxsrZGY1PIcnMF9fPBZwaPAG09QSwYhA/p2O9b/ ZkXtZ2ASkxK5WGIob+zdWgCOUaVfuZYuPNOvkgLxcJ7MMeB0XD9wb+N++CTpf42F5BMn 19KA== X-Gm-Message-State: AA6/9RkAB7XVvfcBMBKdKNrsfeuCk0bcjFpo0fG5WtJF4wpabiTDG25YY7GXcrfDD9Uf0FVf/DA/Z0Sar/GvkQ== X-Received: by 10.31.140.147 with SMTP id o141mr3627473vkd.149.1475723463758; Wed, 05 Oct 2016 20:11:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.0.18 with HTTP; Wed, 5 Oct 2016 20:11:03 -0700 (PDT) In-Reply-To: References: Date: Thu, 6 Oct 2016 10:11:03 +0700 Message-ID: To: Leigh Cc: "pecl-dev@lists.php.net" , PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] Intention to move mcrypt to PECL From: pierre.php@gmail.com (Pierre Joye) 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 has > been migrated, however we voted to move it there. > > Any objections/comments? If not I'll apply for my PECL account in the > 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. Cheers, Pierre