Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Nikita Popov
On Thu, Oct 6, 2016 at 5:22 AM, Davey Shafik wrote: > On Wed, Oct 5, 2016 at 8:11 PM, Pierre Joye wrote: > > > hi Leigh, > > > > On Tue, Oct 4, 2016 at 11:58 PM, Leigh wrote: > > > Hello list, > > > > > > It is my intention to create a new

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Pierre Joye
On Oct 6, 2016 3:41 PM, "Nikita Popov" wrote: > > On Thu, Oct 6, 2016 at 5:22 AM, Davey Shafik wrote: >> >> On Wed, Oct 5, 2016 at 8:11 PM, Pierre Joye wrote: >> >> > hi Leigh, >> > >> > On Tue, Oct 4, 2016 at 11:58 PM, Leigh

[PHP-DEV] Re: [PECL-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Leigh
On 5 October 2016 at 20:11, Derick Rethans wrote: > 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 I'm not sure what you mean by "properly", what steps do you think I'll

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Jakub Zelenka
Hi, On Tue, Oct 4, 2016 at 5: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

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Remi Collet
Le 06/10/2016 à 10:45, Pierre Joye a écrit : > On Oct 6, 2016 3:41 PM, "Nikita Popov" wrote: >> >> On Thu, Oct 6, 2016 at 5:22 AM, Davey Shafik wrote: >>> >>> On Wed, Oct 5, 2016 at 8:11 PM, Pierre Joye wrote: >>> hi Leigh,

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Lester Caine
On 06/10/16 11:12, Jakub Zelenka wrote: > I don't think it can be added to PECL as it breaks its licensing rules > (mcrypt is GPL licensed): It is already an established component in PHP and while it's use has been discouraged for a long time, simply switching it off will break a lot of legacy

[PHP-DEV] GOOD Benchmark Results for PHP Master 2016-10-06

2016-10-06 Thread lp_benchmark_robot
Results for project PHP master, build date 2016-10-06 06:25:28+03:00 commit: 1e986c7 previous commit:3f04ee0 revision date: 2016-10-06 02:15:29+02:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Jakub Zelenka
On Thu, Oct 6, 2016 at 2:46 PM, Dan Ackroyd wrote: > > > > On 6 Oct 2016, at 13:48, Jakub Zelenka wrote: > > > > Looks like copying says LGPLv2 but the files seems to be under GPLv2. See > > for example > > > >

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Dan Ackroyd
> On 6 Oct 2016, at 13:48, Jakub Zelenka wrote: > > 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 Er, unless i'm missing what you mean that file

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Leigh
On 6 October 2016 at 11:12, Jakub Zelenka wrote: > Hi, > > On Tue, Oct 4, 2016 at 5: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 >>

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Ferenc Kovacs
On Thu, Oct 6, 2016 at 12:12 PM, Jakub Zelenka wrote: > Hi, > > On Tue, Oct 4, 2016 at 5: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 > >

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Jakub Zelenka
On Thu, Oct 6, 2016 at 1:38 PM, Leigh wrote: > On 6 October 2016 at 13:35, Ferenc Kovacs wrote: > > > > > > On Thu, Oct 6, 2016 at 12:12 PM, Jakub Zelenka wrote: > >> > >> Hi, > >> > >> On Tue, Oct 4, 2016 at 5:58 PM, Leigh

[PHP-DEV] Re: [RFC] Bug #72811 - Replacing parse_url()

2016-10-06 Thread David Walker
On Thu, Oct 6, 2016 at 11:19 AM Christoph M. Becker wrote: So, I basically see two options: * wait until PHP 8 (whenever that'll be released) and switch the implementation of parse_url() then – what might delay the adoption of PHP 8 * add a new function in PHP

[PHP-DEV] Re: [RFC] Bug #72811 - Replacing parse_url()

2016-10-06 Thread Christoph M. Becker
On 04.10.2016 at 20:14, David Walker wrote: > A couple weeks back I took a look at 72811[1]. The bug being that > parse_url() didn't accept IPv6 addresses without a scheme, like it did for > IPv4 addresses. I attempted to patch the specific bug within the scope of > how parse_url() was

Re: [PHP-DEV] Re: [RFC] Bug #72811 - Replacing parse_url()

2016-10-06 Thread Yasuo Ohgaki
Hi David, On Fri, Oct 7, 2016 at 3:10 AM, David Walker wrote: > * PHP 7.2+ > * Adding parse_uri() as the new RFC compliant parser > * Deprecating the functionality of parse_url() with notice that parser > will change to that of parse_uri() > > * PHP 8.0 > * Alias

Re: [PHP-DEV] [RFC] Bug #72811 - Replacing parse_url()

2016-10-06 Thread Stephen Reay
Could the new URL parser be exposed via a third parameter to parse_url, which defaults to false/off in 7.2 (or whenever its added) but then defaults to true in 8.0? Introducing a new core function to effectively fix a bug seems like the wrong approach to me (and what happens if a new URL/URI

Re: [PHP-DEV] Intention to move mcrypt to PECL

2016-10-06 Thread Leigh
On 6 October 2016 at 13:35, Ferenc Kovacs wrote: > > > On Thu, Oct 6, 2016 at 12:12 PM, Jakub Zelenka wrote: >> >> Hi, >> >> On Tue, Oct 4, 2016 at 5:58 PM, Leigh wrote: >> >> > Hello list, >> > >> > It is my intention to create a new PECL