----- Original Message ----- > Tom Lane (tgl@xxxxxxxxxx) said: > > Yes, that's the general idea --- any dependencies on mysql should > > result > > in installing mariadb, unless the user takes specific action to get > > mysql instead. Ideally we'd just do the standard > > Provides/Obsoletes > > dance for replacing one package with another, but I'm not quite > > sure how > > that should work if we still want original mysql to be installable. > > Any > > thoughts from RPM experts would be welcome. > > > > (If the compatibility testing goes *really* smoothly, maybe we > > could > > just drop the requirement for original mysql to still be available, > > in which case it reduces to the standard package-replacement > > problem. > > But I'm not prepared to bet on that quite yet.) > > Honestly, I'd be curious as to whether we could get all the > compatibility > testing done early enough, and packages changed, such that we could > consider > dropping MySQL. It's just... cleaner. Also I'd even prefer hickups/issues found during this testing (or expected - of course not data loss) as a better thing than shipping hard to maintain mysql - security issues, bugfixes. Not saying that current mysql guys will completely drop mysql support but due to how upstream behaves to mysql + resources put to have a good support for mariadb... Jaroslav > > Bill > -- > devel mailing list > devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/devel -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
