kage it is - i.e. is that
something that was never meant to be in the API/ABI in the first place, or
is an oversight?
I'm also wondering whether it's worth renaming the Debian package from
libmariadb2 to libmariadb2a because of this.
--
Daniel Schepler
t library in Debian.
Likewise, for usr/lib/mysql/plugin/*.so: Versions of those are currently in
usr/lib/x86_64-linux-gnu/plugin/ in the Git Debian packaging for
Connector/C 2.2.2 - though I'm seriously considering changing that to avoid
polluting the namespace with such a generic name.
lexible enough - we need the libraries
to go to e.g. /usr/lib/x86_64-linux-gnu, while the headers should probably
still go to /usr/include/mariadb.
--
Daniel Schepler
___
Mailing list: https://launchpad.net/~maria-developers
Post to : maria-de
e Debian packages I instead
patched mariadb_config to remove the indirect dependencies altogether, as
we generally do, so I didn't write a fix for the -l-lz issue. Also, it seems
that if I try to build with WITH_SQLITE=ON then I get a build error, so I
haven't enabled that in the Debian packag
I recently got the bug report below for the MariaDB C client library
(Debian package). The request to add a compatibility symlink from
mysql_config to mariadb_config makes sense to me -- do you see any
potential problems with adding it?
--
Daniel Schepler
-- Forwarded message
5 matches
Mail list logo
