I think the original idea was: Keep the client configuration common to both MySQL and MariaDB as much as possible. This is because we do want the clients to be coinstallable and also because users often don't have control of the client in use since it goes through a client library they didn't choose to build.
So in this world, client configuration would be shipped by mysql-common only. I may be remembering this wrong, and there might have been a misunderstanding at the time, so I welcome any corrections to this. Then it'd only be the _server packages_ that register against update-alternatives. Only one of the servers can be active at once, which is reasonable. And then there would be no collision, since we already ensure that only one server is active at once. (If we want to allow coinstallable servers then we also need to complete the cooperative handling of /var/lib/mysql that we agreed, as well as disentangle the service files and binaries and default listening ports in addition to /etc/mysql). On Mon, Sep 28, 2020 at 08:57:11PM +0300, Otto Kekäläinen wrote: > I also see that mysql-8.0 added quite a few conflicts on mariadb-*. In > mysql-5.7 only the server conflicted with the mariadb equivalent. [...] > So having any kind of co-installability for even the clients does not > seem possible right now. Then how does this bug arise?
signature.asc
Description: PGP signature
