Newsgroups: php.internals,php.pecl.dev
Path: news.php.net
Xref: news.php.net php.internals:96268 php.pecl.dev:14022
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.50 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAEKnhAGwT-O3nT+V6hgGK+mt=qOaGwhZg_JQqupvL0Bp-Ra1KA@mail.gmail.com>
References: <CAPwsocHA-6PCJ83PSSmACUPWr=+66bTbs7akX8SmOYOrJmH5Sw@mail.gmail.com>
 <CAEKnhAGwT-O3nT+V6hgGK+mt=qOaGwhZg_JQqupvL0Bp-Ra1KA@mail.gmail.com>
Date: Thu, 6 Oct 2016 13:24:49 +0100
Message-ID: <CAPwsocE-aVU87JGMjZ1v0k7Qeb6wSqQHJweJ+pUwUmeqKabo0Q@mail.gmail.com>
To: Jakub Zelenka <bukka@php.net>
Cc: pecl-dev@lists.php.net, PHP internals list <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] Intention to move mcrypt to PECL
From: leight@gmail.com (Leigh)

On 6 October 2016 at 11:12, Jakub Zelenka <bukka@php.net> wrote:
> Hi,
>
> On Tue, Oct 4, 2016 at 5:58 PM, Leigh <leight@gmail.com> 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 don't think it can be added to PECL as it breaks its licensing rules
> (mcrypt is GPL licensed):
>
> Note: wrappers for GPL (all versions) or LGPLv3 libraries will not be
> accepted. Wrappers for libraries licensed under LGPLv2 are however allowed
> while being discouraged.
>
> See https://pecl.php.net/account-request.php
>
> Cheers
>
> Jakub
>

Interesting, thanks for that.