Bug#702280: libdbd-mysql-perl / mariadb update
This pre-wheezy bug (#702280) about libdbd-mysql-perl vs. MariaDB has
been quiet for a while, but it would be good to reach some conclusion
for stretch. Taking the debian-perl@ list in the loop.
Reading Otto's recent announcement at
https://lists.debian.org/debian-devel-announce/2016/09/msg00000.html
the simplest thing seems to be to just start build depending on
default-libmysqlient-dev. This would mean we only provide DBD::mysql
linked against the mysqlclient variant (including MariaDB) that's been
chosen as the default by the project, presumably the release team.
All the other alternatives seem too complex to me:
- I don't think we're going to start providing a DBD::mariadb when
upstream doesn't
- while it would probably be possible to offer two conflicting DBD::mysql
packages linked against different mysqlclient libraries, that seems
overkill to me. Would we need a default-libdbd-mysql-perl next?
- I'm not sure if alternative runtime dependencies on libmysqlient18 |
libmariadbclient18 were ever possible, but at least they aren't on
current sid (libmysqlclient.so.* is only in the src:mysql-* packages)
I propose we adopt the default-libmysqlient-dev solution unless somebody
objects?
FWIW, it looks like Fedora has been offering DBD::mysql linked
against MariaDB for a while already, and upstream seems receptive (see
lib/DBD/mysql/INSTALL.pod).
--
Niko Tyni ntyni@debian.org
Reply to: