[debian-mysql] percona vs. mariadb

[Otto Kekäläinen]

Hello,

2013/3/15 Clint Byrum <spamaps at debian.org>:
[..]
> /var/lib/mysql for mysql. /var/lib/mariadb for mariadb. If an admin
> wants to migrate between the two, I suggest they think that through
> *very* clearly and use the method that makes the most sense for them
> (symlinks.. bind mounts, manual mv'ing files/dirs).

This would be good, I'll investigate what it means for packaging at
the moment when upstream MariaDB hasn't adopted this way of doing
things (at least yet?). I hope it will be just a simple path issue,
not a huge patch with lots of maintenance burden.

[...]
>> At some point in the future, if they really diverge from each other,
>> they could adapt separate configs (compare how httd providers Apache
>> and Nginx are packaged in Debian). But I think these kind of diverges
>> are initiated in the upstream project, and not designed nor maintained
>> by downstream packagers.
>>
>
> IMO they must use separate configs now.

I'll take a look at this too see how big of an change it would be.

[...]
>> Now to the question, how many MySQL variants could Debian ship? I
>> don't know, but I assume that Debian should at least have MySQL plus
>> some other that users can migrate to in case Oracle goes evil. More is
>> of course better, but only it there are resources.
>>
>
> You're suggesting the way Oracle is abusing MySQL's community isn't evil?
>
> Ignoring test cases and re-inventing fixes to known bugs just for the
> sake of pretending like you can have a non-full-disclosure open source
> database is pretty evil already.

Yes, Oracle is evil, I was just tying to be polite and not say it as
an absolute fact yet..


[..]
>> So I suggest we keep MySQL for at least one cycle and include MariaDB
>> ASAP, so that both will be available and users can vote themselves
>> running either "apt-get install mysql-server" or "apt-get install
>> mariadb-server".
>>
>
> +1, but no time limit. As long as users are ok with the way things work
> with MySQL, I'm comfortable with continuing to maintain it. Thus far
> we've had a single regression reported due to shipping newer patch
> releases, and that one was basically "really old and busted stuff
> stopped working".

Yes, *at least one cycle* and probably longer, but one cycle is bare
minimum so that there is time to adapt.

I'll get back to you later when I've finished the two packaging
changes presented above. Thanks for your feedback!

- Otto