On Sat, Nov 22, 2014 at 2:11 PM, Otto Kekäläinen <o...@seravo.fi> wrote:

> Package: libmariadb-client-lgpl-dev
>
> I decided to forward the message from Arnaud Fontaine below as a bug
> report so we can work on it using the normal Debian bug tracking
> processes.
>
> My quick opinion is that we cannot use upstream libmysqlclient as it
> conflicts with Oracle libmysqlclient in Debian in ways senior DDs
> don't accept and renaming to libmariadbclient wasn't adopted by
> anybody downstream, so using only mariadb-client-lgpl is still our
> best shot - maybe upstream mariadb-client-lgpl developer could solve
> this by merging the missing features from mysql_configure to
> mariadb_configure?
>

I don't see how the client-only library build would get information about
where the mariadb plugin headers are located.  Maybe the mariadb packages
could provide something like mariadb_plugin_config instead?  And/or we
could add pkg-config and cmake config files, and deprecate the *_config
binaries.
-- 
Daniel Schepler

Reply via email to