Otto Kekäläinen <o...@seravo.fi> writes: > Upstream MariaDB only ships with libmysqlclient.so, while I have > changed the Debian version to ship the library using the name > libmariadbclient.so, because I got feedback that it is not good policy > for the MariaDB package to ship a so name that also exists in another
It seems to me that based on this, it would be reasonable to drop the Provides: libmysqlclient-dev for the native Debian packages of libmariadbclient-dev. If a Debian package wants to build with the MariaDB client library, it can use libmariadbclient-dev as a build dependency. If it wants to use the Oracle/MySQL client library, it can use libmysqlclient-dev instead. It actually seems to be wrong for one -dev package to Provide: the other, doesn't it? In the third-party repository packages, we had the Provides: libmysqlclient-dev. This was necessary, because the real libmysqlclient-dev package was not co-installable with libmariadbclient. So it became impossible to build any package that depended on libmysqlclient-dev without uninstalling the MariaDB server; the Provides: libmysqlclient-dev solves this. But if I understand correctly, now it is possible to install packages libmariadbclient and package libmysqlclient-dev at the same time. So the problem should no longer apply. (libmariadbclient-dev and libmysqlclient-dev are not co-installable, but it is my understanding that this is not a problem as such, as it is only a build dependency, not a runtime dependency). Hope this helps, - Kristian. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org