Hi, > 1) B-D: > > - Dual compatibility: If the package actively supports both engines and you > > wish > > to keep an alternative runtime path open for users drawing from > > third-party > > repositories, you can declare an OR dependency. For example > > 'Depends: mariadb-client | mysql-client'. > > Whats the correct Build-Depends equivalent? src:pdns uses a > (comparatively small) libmysqlclient API surface.
I haven't tested, but I'd guess the pdns should have `Build-Depends: libmariadb-dev` or `Build-Depends: libmariadb-dev-compat`. Based on https://github.com/PowerDNS/pdns/blob/36f6762677539abd610f33fc48310bcf39defe05/docs/upgrading.rst#430-to-431 seems PowerDNS has been updated to use `mariadb` directly and no longer needs the compat shim that provides `mariadb` using the library name `mysql`. > 2) We'll need an answer to > https://lists.debian.org/debian-devel/2026/05/msg00256.html > as we intend to keep the same source package buildable across Debian > and Ubuntu. > > 3) We'll need B-D: and D: stanzas that work across bookworm and > newer, as we intend to keep the same source building across these. I > imagine the mariadb and mysql packages might have stayed stable > enough in that timeframe, but please advise if this is really true. Because you prefer using the same source everywhere, it probably makes sense for you to postpone doing major changes until a) Forky freeze is imminent or b) some other change surfaces that forces you to deal with compatibility issues immediately. Based on PowerDNS docs like https://doc.powerdns.com/authoritative/backends/generic-mysql.html it seems the DB use in general is very generic and works fully with both MySQL and MariaDB for now. I don't see any traces of anyone testing it with MySQL 9.4 or MariaDB 12.3, so the future compatibility situation remains unknown.
