2014-04-01 15:14 GMT+03:00 gregor herrmann <gre...@debian.org>: > I might be missing something, but this still seems impossible. In > order to build both flavours, we'd need to build-depend on both > libmariadbclient-dev and libmysqlclient-dev, but libmariadbclient-dev > still seems to have a "Breaks: libmysqlclient-dev" which makes the > two packages not co-installable.
Yes, your right, it isn't possible. Actually what would be needed is to have two separate source packages which are almost identical, except for the client library soname. Would you by any chance feel like you would like to maintain an extra libdbd-mariadb-perl package? > (Besides that we'd have to think if we want to name the binary > package libdbd-mariadb-perl and/or if we want to make some more > changes to it and/or if it should Conflict/Break libdbd-mysql-perl > etc. But that's for later ...) Both packages should probably co-exist for a long time. They should probably break/replace each other. The filenames are the same inside the -perl package, so they cannot be co-installable. The libs libmysqlclient18 and libmariadbclient18 are co-installable, as the filenames are different, but at the moment the equivalent -dev packages conflict, as those share same paths and filenames. This is actually getting more and more complex as I think about it. Anyway, MariaDB is now in Debian side-by-side with MySQL. Feel free to design a way to use it, you might have a better take on this challenge than what I do, at least for the moment. -- Check out our blog at http://seravo.fi/blog and follow @ottokekalainen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
