... > Does anyone have thoughts on how to best deal with documentation and > naming related to this?
If your current package desciption only mentions MySQL, it would make sense to update the text to say e.g. "MariaDB/MySQL" to make it clear that both are supported. This pattern is common, see e.g. https://docs.rsyslog.com/doc/configuration/modules/ommysql.html as an example of upstream doc that says "ommysql: MariaDB/MySQL Database Output Module". Whether or not you rename packages is up to you, and depends a the upstream situation. Reading out to your own upstream to ask which database their are using in their CI and what they are developing against and what future plans they have will most likely help you decide what is the most sensible thing to do for your specific package Debian. I already saw in e.g. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137779#37 an upstream rsyslog dev chime in and share their current status and future plans. ... > Proposed new version: > > Description: NSS module for using MariaDB as a naming service > libnss-mysql provides a Name Service Switch module that allows MariaDB > to act as a name service. > . > Its configuration is very flexible by allowing to set an SQL query per NSS > call (getpwnam, getpwuid, ...). > . > It currently supports storage of passwd, group and shadow information. > . > While upstream supports MySQL, this package only supports MariaDB since > MySQL is not packaged by Debian. This seems fine to me in this case. There is no best practice yet - we are now establising it with these discussions. As the maintainer are probably in the best position to decide. Others can then look what you did and perhaps follow your lead after seeing how well it worked for your package.
