Hi Julian, I'm not very keen on failing preinsts.
You seem to be making an assumption that your data will still be readable after switching from MySQL to MariaDB. However, I don't make that assumption if I switch from MySQL to Postgres. One difference is that the MySQL and MariaDB packages do conflict, for various reasons. This is fundamental as they both listen on the same port (and pretty much speak the same protocol) by default. However, I don't think this is enough of a reason to rely on a user assumption which simply isn't true upstream, and that we don't advertise. I think the right thing to do is the same as the MySQL->Postgres scenario. The data should be able to stay put. The new daemon should start (perhaps with a new empty database, as MariaDB is currently doing if I understand correctly). And the user should be able to seamlessly switch back. That the packages conflict shouldn't come in to it. Separately, mysqldump isn't in mysql-server-core-5.7. Could it be, and if it could, would this be conflict-free? Robie
signature.asc
Description: PGP signature
