On 2018/05/24 12:49, Martijn van Duren wrote: > Hello ports@, > > Currently sqlite in PHP builds its own sqlite and links it internally. > This library is quite out of date (3.8.10.2 for 5.6 and 3.14.2 for 7.0). > > I would like to link PHP to our sqlite3 package, so that it can be kept > up to date. This is assumed to also be what happens with most Linux > packages[0].
That makes sense to me. > The motivation to split pdo_sqlite/sqlite3 into a separate package is > for two reasons: > 1) All other databases have their own package, so it's more consistent. > 2) Keeping the extensions in the SAPI would add another dependency on > the PHP-main package. > > Of course I can change the patch to just link to the sqlite package > if this is not enough motivation to split them up. > > If we split them up the packages that at least have sqlite calls in > them are, but might be in optional code-paths: > icinga/web2 > zabbix-agent > chive > nextcloud > owncloud > piwik It's definitely more than that - I know roundcube needs pdo_sqlite or another pdo_* - you'd need to look for things using pdo at all to find them, rather than just looking for sqlite. Splitting up database extensions with library deps does seem reasonable but I'm wondering maybe we should merge the $somedatabase and pdo_$somedatabase packages, I'm not sure there's much point in splitting them up, and that way the total number of subpackages doesn't increase.. www/chive is removed already btw.
