Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:103167
To: PHP internals <internals@lists.php.net>
Message-ID: <381a49ae-eed5-889a-8d0c-bec4b4531d82@gmx.de>
Date: Mon, 17 Sep 2018 15:16:13 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
 Thunderbird/60.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 8bit
Subject: Unbundle libsqlite3?
From: cmbecker69@gmx.de ("Christoph M. Becker")

Hi!

We bundle an unmodified libsqlite3 for at least two years.  Since then
all updates go into any dev, alpha and beta releases, while security
patches (usually backports from libsqlite3) go into stable branches.

ext/sqlite3 requires libsqlite ≥ 3.3.9[1] which has been released on
2007-01-04[2] (i.e. more than eleven years ago!).  ext/pdo_sqlite has no
specific version requirement; there is a check for sqlite3_open()[3]
which I believe is available since 3.0.0.

So is there any particular reason why we still bundle libsqlite3?

[1]
<https://github.com/php/php-src/blob/php-7.3.0RC1/ext/sqlite3/config0.m4#L37-L47>
[2] <https://sqlite.org/oldnews.html#2007_01_04>
[3]
<https://github.com/php/php-src/blob/php-7.3.0RC1/ext/pdo_sqlite/config.m4#L55-L58>

-- 
Christoph M. Becker