Newsgroups: php.internals,php.pecl.dev
Path: news.php.net
Xref: news.php.net php.internals:96271 php.pecl.dev:14025
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.217.175 as permitted sender)
MIME-Version: 1.0
Sender: jakub.php@gmail.com
In-Reply-To: <CAPwsocGQaS4OPtBPxF8gDs=H0gB6DJ7H4Fa25v83QznTjuXGOA@mail.gmail.com>
References: <CAPwsocHA-6PCJ83PSSmACUPWr=+66bTbs7akX8SmOYOrJmH5Sw@mail.gmail.com>
 <CAEKnhAGwT-O3nT+V6hgGK+mt=qOaGwhZg_JQqupvL0Bp-Ra1KA@mail.gmail.com>
 <CAH-PCH4gfedM4zT4paxHBZcaUkgF=b-XWwWf_iT3aODG0Yc3MA@mail.gmail.com> <CAPwsocGQaS4OPtBPxF8gDs=H0gB6DJ7H4Fa25v83QznTjuXGOA@mail.gmail.com>
Date: Thu, 6 Oct 2016 13:48:48 +0100
Message-ID: <CAEKnhAHnxyAFSd0rbefBNby2XwsphfLqLL9EV+XQ0izofAQYTQ@mail.gmail.com>
To: Leigh <leight@gmail.com>
Cc: Ferenc Kovacs <tyra3l@gmail.com>, PECL Announce <pecl-dev@lists.php.net>, 
	PHP internals list <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=001a1140a22212b9a8053e31b775
Subject: Re: [PHP-DEV] Intention to move mcrypt to PECL
From: bukka@php.net (Jakub Zelenka)

--001a1140a22212b9a8053e31b775
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 6, 2016 at 1:38 PM, Leigh <leight@gmail.com> wrote:

> On 6 October 2016 at 13:35, Ferenc Kovacs <tyra3l@gmail.com> wrote:
> >
> >
> > On Thu, Oct 6, 2016 at 12:12 PM, 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 ha=
s
> >> > been migrated, however we voted to move it there.
> >> >
> >> > Any objections/comments? If not I'll apply for my PECL account in th=
e
> >> > 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 no=
t
> be
> >>    accepted. Wrappers for libraries licensed under LGPLv2 are however
> >> allowed
> >>    while being discouraged.
> >>
> >> See https://pecl.php.net/account-request.php
> >>
> >> Cheers
> >>
> >> Jakub
> >
> >
> > AFAIK mcrypt is gpl, libmcrypt (wrapped by our mcrypt ext) is lgpl so i=
t
> > would be fine for pecl.
> >
> > --
> > Ferenc Kov=C3=A1cs
> > @Tyr43l - http://tyrael.hu
>
> http://mcrypt.cvs.sourceforge.net/viewvc/mcrypt/libmcrypt/
> COPYING.LIB?revision=3D1.1.1.1&view=3Dmarkup
>
> LGPLv2
>

Looks like copying says LGPLv2 but the files seems to be under GPLv2. See
for example

http://mcrypt.cvs.sourceforge.net/viewvc/mcrypt/libmcrypt/lib/mcrypt.h.in?v=
iew=3Dmarkup

That's why I thought it's GPL. Not sure what's more important though...

Cheers

Jakub

--001a1140a22212b9a8053e31b775--