On Thu, Oct 6, 2016 at 1:38 PM, Leigh <lei...@gmail.com> wrote: > On 6 October 2016 at 13:35, Ferenc Kovacs <tyr...@gmail.com> wrote: > > > > > > On Thu, Oct 6, 2016 at 12:12 PM, Jakub Zelenka <bu...@php.net> wrote: > >> > >> Hi, > >> > >> On Tue, Oct 4, 2016 at 5:58 PM, Leigh <lei...@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 > > > > > > AFAIK mcrypt is gpl, libmcrypt (wrapped by our mcrypt ext) is lgpl so it > > would be fine for pecl. > > > > -- > > Ferenc Kovács > > @Tyr43l - http://tyrael.hu > > http://mcrypt.cvs.sourceforge.net/viewvc/mcrypt/libmcrypt/ > COPYING.LIB?revision=1.1.1.1&view=markup > > 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?view=markup That's why I thought it's GPL. Not sure what's more important though... Cheers Jakub
