Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103306
To: Eihab <eihabibrahim@gmail.com>, Internals <internals@lists.php.net>
References: <fdfdca90-20a9-b929-ac0c-42a3d0321396@gmx.de>
 <E7C6FDEC-1C17-4E33-9992-4398D544DDD1@gmail.com>
Message-ID: <41cf3346-1146-7164-aa16-c3d472cf2fe1@gmx.de>
Date: Sun, 7 Oct 2018 00:17:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.2.1
MIME-Version: 1.0
In-Reply-To: <E7C6FDEC-1C17-4E33-9992-4398D544DDD1@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] ext/dba: drop support for Berkeley DB < 4
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 06.10.2018 at 20:10, Eihab wrote:

> Is it broken?
> 
> Are you personally maintaining it and it’s becoming a burden?
> 
> Is the binary size too big because of it?
> 
> Does the code cause a significant security risk?

Good questions, but in my opinion the relevant first question here is:
“is there a significant number of users who need BDB < 4 support in
future PHP versions?”  Otherwise I see no point in putting further
maintance effort (see, for instance, the dba_db2.c history[1]) just to
let the extension compile (I suppose that nobody of the PHP team
actually tested with BDB < 4 within the last years).

[1] <https://github.com/php/php-src/commits/master/ext/dba/dba_db2.c>

-- 
Christoph M. Becker