Status with latest version in Bookworm:

$ dpkg -l | grep libmariadb-dev-compat
ii  libmariadb-dev-compat:amd64 1:10.11.2-1

$ mysql_config --version
10.11.2

$ mariadb-config --version
10.11.2

$ grep ^Version /usr/lib/*/pkgconfig/libmariadb.pc
Version: 3.3.4

$ find /usr/lib/*/pkgconfig/m*.pc -ls
pkgconfig/mariadb.pc -> libmariadb.pc
pkgconfig/mysqlclient.pc -> libmariadb.pc


Status in Docker image debian:buster-20230109

$ dpkg -l | grep libmariadb-dev-compat
ii  libmariadb-dev-compat:amd64 1:10.3.36-0+deb10u2

$ mysql_config --version
10.3.36

$ mariadb-config --version
bash: mariadb-config: command not found

$ grep ^Version /usr/lib/*/pkgconfig/libmariadb.pc
Version: 3.1.18

$ find /usr/lib/*/pkgconfig/m*.pc -ls
pkgconfig/mariadb.pc
pkgconfig/mysqlclient.pc -> mariadb.pc


I have no idea why this is so but agree that mariadb-config not being
same version as mariadb.pc is confusing.



Related upstream PRs that do not fix this but are on the same topic:
- https://github.com/mariadb-corporation/mariadb-connector-c/pull/219
"Return correct client library version number"
- https://github.com/MariaDB/server/pull/1800 "MDEV-23538: Rename
mariadb.pc to libmariadbd.pc to avoid confusion"

Reply via email to