Thanks, I have a lot to learn. Yes, this is perfect. Bill On 7/21/2023 10:38 AM, Matthew Newton via Freeradius-Users wrote:
On 21/07/2023 16:25, Bill Schoolfield wrote:
control.in requires: default-libmysqlclient-dev | libmysqlclient-dev
I did install default-libmysqlclient-dev and freeradius built w/o error and rlm_sql is working.
On Debian12, default-libmysqlclient-dev is a metapackage, it contains no files (except a changelog) and depends on libmariadb-dev-compat.
libmariadb-dev-compat depends on libmariadb-dev. The only significant "files" it contains are symlinks from the mysql library filenames to their mariadb counterparts.
So I now have mysql and mariadb client libraries on this host. Our clients (apps) use the latter, freeradius uses the former to "talk" to a mariadb server. While I'm sure there are some differences these should be interchangeable. Seems unnecessary or maybe even ugly to have both though.
They're all the same files just symlinked, so there's no possibility of any conflicts.
While working this I realized we have the same situation with our perl scripts elsewhere that use DBI /DBD. They presently use mysql as well.
As I said before, I'm pretty sure Debian 12 doesn't have mysql at all. It's all mariadb, but with compatibility names as everyone's called it mysql for ever.
In fact, yes:
root@55172a6329fe:/# apt-cache search mysql-server mariadb-server - MariaDB database server binaries mariadb-server-core - MariaDB database core server files default-mysql-server - MySQL database server binaries and system database setup (metapackage) default-mysql-server-core - MySQL database server binaries (metapackage)
I don't think you need to worry about anything. Using the packages we build will save you from having to build anything, too, if you wanted.