On Sat, 24 Sep 2016 16:04:36 +0300, Niko Tyni wrote: > 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.
Thanks for bringing this up. It was on my radar as well but more in the outer region of the scanned area :) > 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. Right, that was my conclusion as well. What I'd like to see is - a confirmation that this is indeed the final decision, since there was a discussion round default-libmysqlient-dev on -devel after the announcement; - maybe someone to test the package; I once built it against default-libmysqlient-dev and didn't see any problems but the test suite is basically doing nothing as it needs a mysql/mariadb server with a database and user etc. > 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). Ah, cool. Cheers, gregor -- .''`. Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - https://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Joe Cocker: I Stand In Wonder
signature.asc
Description: Digital Signature
