On Sun, 2012-10-28 at 23:31 +0100, Kevin Kofler wrote: > Sven Lankes wrote: > > mariadb will need to conflict with the default mysql packages > > which is usually not allowed in fedora. So this is going to > > be interesting. > > Uh, conflicting with MySQL is really a no go (just look at how many things > require mysql-libs, and even mysql-server is required for Akonadi, and > mysql-embedded or Amarok), why isn't the fork renaming its stuff? If the > idea is to be a 100% compatible drop-in replacement, then Fedora needs to > make a choice whether to ship Oracle's MySQL or MariaDB and then stick to > it. Well, we could also take the approach we take with MTAs; have a set of generic virtual Provides for MySQL-alikes and have all the MySQL-alikes we package Provide these, as well as Providing their own specific name, and conflict with each other. Just like postfix, qmail and sendmail all Provide: smtpd and conflict with each other. It would be some packaging effort, but it would resolve the issue cleanly. This would fly so long as it's expected that there will be a long-term future for the 'MySQL-alike' world in which we have multiple competing implementations that are mutually compatible for many client apps. I'm not involved enough in the area to know if that's true. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
