Newsgroups: php.internals,php.pecl.dev
Path: news.php.net
Xref: news.php.net php.internals:96258 php.pecl.dev:14013
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender)
Date: Wed, 5 Oct 2016 15:11:28 -0400 (EDT)
To: Leigh <leight@gmail.com>
cc: pecl-dev@lists.php.net, internals@lists.php.net
In-Reply-To: <CAPwsocHA-6PCJ83PSSmACUPWr=+66bTbs7akX8SmOYOrJmH5Sw@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1610051510420.4972@whisky.home.derickrethans.nl>
References: <CAPwsocHA-6PCJ83PSSmACUPWr=+66bTbs7akX8SmOYOrJmH5Sw@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Subject: Re: [PECL-DEV] Intention to move mcrypt to PECL
From: derick@php.net (Derick Rethans)

On Tue, 4 Oct 2016, 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.

It should be migrated properly, and also to GIT. I prefer that it is 
released with my username as "lead", as I wrote a big deal of it.

cheers,
Derick