Le 22/09/2022 à 18:12, Robie Basak a écrit :
On Thu, Sep 22, 2022 at 05:10:05PM +0200, nobody wrote:* What outcome did you expect instead?installing a client library should not require anything on the server side and should not modify server configuration of mariadb or other mysql flavors (imho ;p)Both MySQL/MariaDB client libraries and MySQL/MariaDB daemons expect and use /etc/mysql/my.cnf, and many common packages supplied by Debian link to a MySQL/MariaDB library. So Debian ends up needing to ship a working /etc/mysql/my.cnf essentially by default. It doesn't matter which side of the fork is in use - it's necessary either way. Maybe upstream could separate the two out, but they don't.
thanks for your quick answer So perhaps we could see it another way : in this particular case i think that a client library, if it find an existing /etc/mysql/my.cnf, should not do anything as it is there adn so everything it need is okay. There is no need for a client library to change this part if it is here if it only need one to exist. Perhaps just adding a check if [[ ! -e /etc/mysql/my.cnf ]]; then do touch server configuration in /etc/mysql/my.cnf fi -- cordialement, Ghislain ADNET.
