On Tue, Aug 26, 2014 at 02:52:34PM +0200, Kristian Nielsen wrote: >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?
Definitely, *unless* you're actually providing a cleanly compatible implementation in all respects - headers, libraries, API and ABI. If you're not, then don't pretend to be in the packaging system. -- Steve McIntyre, Cambridge, UK. st...@einval.com Support the Campaign for Audiovisual Free Expression: http://www.eff.org/cafe/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org