Hi, > So let me rephrase the request. `mysql_config --version` and `pkgconf > --modversion mysqlclient` should report the same version (without making > claims as to which version that is anymore). > > Do you find that view agreeable?
Yes ... > > Do you think I should take > > https://github.com/mariadb-corporation/mariadb-connector-c/pull/219 > > and apply it in MariaDB packaging in Debian permanently? Seems > > upstream wants mariadb.pc to emit the client version, not server > > version, but I can deviate from upstream if there are good grounds to > > do so. > > I fear that there are no good answers here. You can only choose between > wrongs. As has been pointed out in that pull by rmk92, this is not > primarily a Debian problem. > > As a result of what happened, querying the mysql client library for its > version has become a practically useless endeavour. Depending on whether > you use mysql or mariadb you get completely different versions and > depending on whether you ask with pkgconf or mysql_config you also get > completely different versions even for mariadb. Bottom line is that this > interface is ruined. Upstream didn't accept my PR nor the motivations why the API should not break like this. But they didn't reject that PR either. And since time has passed, I agree with your conclusion above about the interface being ruined now and there is no going back anymore. > At this point, I don't think it matters much anymore, but deviating from > upstream is only worsening the problem as that adds another angle to the > mess. What we'll have to do is delete all version checks from upstream > software. That's the only practical way forward sadly. Agree, let's align with upstream in forky so people having issues will at least have the same issues as everyone else compiling against MariaDB using the 'mysqlclient' reference.
