I can certainly understand the interest in switching to MariaDB -- though personally I'm not at all convinced 12.3 is the right time/place to do so -- but I am concerned about the assumption that "drop in replacement" really is. That may be a goal, but it most certainly in not 100% true. Starting here, @MariaDB project itslef, https://kb.askmonty.org/en/mariadb-versus-mysql-compatibility/ http://blog.mariadb.org/mariadb-10-0-and-mysql-5-6/ and recognizing that large projects that use MySQL API/libs/engines (e.g., Drupal, PHP, etc) still recognize/experience differences between MySQL and the main forks, making that assumption has real potential to wreak havoc. I'd suggest that if a change of distro default is being made to MariaDB, *and* there is an ongoing commitment to offer an official MySQL pkg in the distro, that the pkg namespaces should be completely & clearly separated, and that -- unless and until 100% compatibility can be guaranteed -- a separate devel pkg , libs & includes, be made available. I haven't yet thought through the differences between MySQL packaging for a integrated-distro-default-switch, vs. as a standalone server ... if any. Michal's packages for MySQL56 (which I use ... ), e.g., have been great/stable for ages. These MariaDB changes percolated quietly into server:database repo, and caught me unaware -- causing some breakage. Michal was great about helping in #irc, and the issues were easily fixed, and this announcement is great to see, but, I think this switch should be done carefully. True, many users won't notice a difference. Otoh, there's real potential to cause trouble, as well. Daryl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org