Hi,
* Preuße, Hilmar <[email protected]> [260529 09:47]:
Am 29.05.2026 um 09:00 schrieb Simon Josefsson:
[..]
I thought about dropping 'MySQL' here and only refer to MariaDB, but
that begs the question about the name of the package. But that's an
upstream matter, and upstream probably supports MySQL still too, so
I doubt they rename this to libnss-mariadb.
I have a similar issue with proftpd-mod-mysql. I tend to make the
proftpd-mod-mysql a transitional package, which pulls in the
to-be-created package proftpd-mod-mariadb.
In cases when users are expected to handle the actual name, I think
it is not helpful to rename the package. F.e. for proftpd, where
users will have to configure the mysql plugin - I see little point
in the rename.
You could fully rename the package, the plugin, config files, sed
mysql with mariadb in all documentation etc. But will that help
anyone?
I'd wait with any package renames for such cases until the moment
*upstream* renames. Adding MariaDB to the package description would
be helpful obviously.
Best,
Chris
