I can do: MySQL/MariaDB
in https://salsa.debian.org/php-team/php/-/blob/debian/main/8.4/debian/rules.d/ext-mysql.mk?ref_type=heads description field. Anything more would be too complicated as the d/control is generated. Ondrej -- Ondřej Surý (He/Him) > On 18. 12. 2025, at 1:04, [email protected] wrote: > > On 2025-12-17 08:46, Ondřej Surý wrote: >> Control: close -1 98 >> >> No, the php-<ext> describes the name (or the namespace) of the modules >> inside the package. I am sorry, but this bug has no merit. > > Thanks for clarifying the naming convention around php-<ext>, that > helps. > > Given that MariaDB has been the main MySQL-compatible server in Debian, > and upstream PHP explicitly lists MariaDB Server as a supported backend > for the MySQL protocol drivers, I was mostly just curious if you see any > room at all for that to be reflected in the PHP packaging metadata in > the future, or if you would prefer to keep everything expressed entirely > via php-mysql. > > For context, WordPress public stats [1] show that a majority (about 57%) > of WordPress sites report running on MariaDB today, so a lot of PHP apps > are effectively developed and tested against MariaDB, even if they > currently just depend on php-mysql in Debian. > > [1] https://wordpress.org/about/stats/#mysql_version > > Aquila > >> >> Ondrej >> -- >> Ondřej Surý (He/Him) >> [email protected] >> >>>> On 17. 12. 2025, at 1:24, [email protected] wrote: >>> >>> Package: php-defaults >>> X-Debbugs-Cc: [email protected], [email protected] >>> Version: 98 >>> Severity: wishlist >>> >>> Hi, >>> >>> I would like to add a php-mariadb metapackage in php-defaults. >>> >>> While the upstream PHP modules use the name 'mysql', they are used with >>> MariaDB in a growing number of projects. Introducing a php-mariadb >>> metapackage would allow packages to explicitly express that they are >>> developed/built with MariaDB, and if in future the upstream php-mysql >>> module gains options that are specifically meant for MariaDB, this >>> php-mariadb metapackage could be updated to point to it. >>> >>> Additionally, as Debian uses MariaDB as the default MySQL-compatible >>> server, it feels odd for most PHP reverse dependencies to depend on a >>> package called php-mysql. The upstream PHP documentation >>> (https://www.php.net/manual/en/set.mysqlinfo.php) describes the "MySQL" >>> extensions as MySQL protocol drivers over mysqlnd and explicitly lists >>> MariaDB Server as a supported backend, so it is not wrong for a >>> PHP/MariaDB program to depend on php-mysql, but having an alternative >>> metapackage using the name php-mariadb seems like good preparation for >>> the future. >>> >>> Locally I have the following addition in debian/control.in: >>> >>> Package: php-mariadb >>> Architecture: all >>> Depends: php-common, >>> php@PHP_VERSION@-mysql, >>> ${misc:Depends} >>> Description: MariaDB/MySQL module for PHP (meta) >>> >>> There is no behaviour change for existing users: php-mysql stays as it >>> is and continues to pull in php@PHP_VERSION@-mysql. php-mariadb is an >>> additional metapackage that reverse dependencies can opt into if they >>> want a MariaDB-first dependency that matches the current default and the >>> upstream docs. >>> >>> I'll open a Salsa merge request for php-team/php-defaults implementing >>> this and reference this bug there. >>> >>> Best regards, >>> >>> Aquila
