Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:103169 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41470 invoked from network); 17 Sep 2018 18:39:15 -0000 Received: from unknown (HELO mail.experimentalworks.net) (84.19.169.162) by pb1.pair.com with SMTP; 17 Sep 2018 18:39:15 -0000 Received: from kuechenschabe.fritz.box (ppp-188-174-112-8.dynamic.mnet-online.de [188.174.112.8]) by mail.experimentalworks.net (Postfix) with ESMTPSA id CF2B7481FD; Mon, 17 Sep 2018 16:45:07 +0200 (CEST) Message-ID: <1537195494.22466.5.camel@schlueters.de> To: "Christoph M. Becker" , PHP internals Date: Mon, 17 Sep 2018 16:44:54 +0200 In-Reply-To: <381a49ae-eed5-889a-8d0c-bec4b4531d82@gmx.de> References: <381a49ae-eed5-889a-8d0c-bec4b4531d82@gmx.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Unbundle libsqlite3? From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Mo, 2018-09-17 at 15:16 +0200, Christoph M. Becker wrote: > So is there any particular reason why we still bundle libsqlite3? An issue is that users often  don't control the version being used and SQLite adds features to it's SQL dialect from time to time. At the moment, with the bundled version you can be quite certain that a PHP version maps to a SQLite version, so when migrating to a different host you're going to have the same feature set available.  (Or is that not true since Linux distros don't like using bundled libs, but prefer system installed shared libs so they just upgrade that on security issues?) Most other libraries don't impact in regards to features as much as newer library features would often have to be exported to userspace explicitly. johannes