Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.5, 10.6
Description
Currently we ship libmariadb.pc (for building against the client library) and mariadb.pc (to build against the server). The latter one is confusing to it's name. I've noticed many people assume mariadb.pc is the client library config.
To avoid ambiguity, I suggest that in MariaDB 10.6 we rename it to mariadbd.pc (instead of mariadb.pc). Or even libmariadbd.pc (to be symmetric with libmariadb.pc). The -d is used in libmariadbd package names already and is kind of a convention.
As a bonus, this would help avoid some Lintian complaints that stem from this naming scheme confusion:
W: libmariadb-dev: pkg-config-references-unknown-shared-library usr/share/pkgconfig/mariadb.pc -lz (line 22)
|
W: libmariadb-dev: pkg-config-references-unknown-shared-library usr/share/pkgconfig/mariadb.pc -lssl (line 22)
|
W: libmariadb-dev: pkg-config-references-unknown-shared-library usr/share/pkgconfig/mariadb.pc -lcrypto (line 22)
|
Attachments
Issue Links
- relates to
-
MDEV-14340 packageconfig file in the wrong location
-
- Closed
-
-
MDEV-14921 Fix mariadb/mysql client library packaging for MariaDB 10.3
-
- Closed
-
-
MDEV-21869 Make MariaDB 10.5 Lintian clean (Debian quality assurance tool)
-
- Stalled
-
the naming pattern with lib* is more common, but not overwhelmingly. About 1/3rd of all *.pc files have lib* prefix. On my laptop it's 136 lib*.pc files and 299 without lib*.
So I'd rather stick to the lib* old names for backward compatibility reason. I just don't see a good reason to break existing applications that check for libmariadb.pc.