Am 30.10.2012 01:08, schrieb Adam Williamson:
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.
you can not compare a more or less standalone MTA with a package
like mysql-libs where endless packages linked against!
i doubt MariaDb would be interface-compatible in most cases
BUT not binary comatible as you can also not replace MySQL 5.1
against MySQL 5.5 without compat-packages (remi did outside
fedora-packages) as long depending packages are linked against
a specific version
PLEASE be careful to replace mysql distribution-wide
i do not buy the 100% compatible argument in all cases