[debian-mysql] Request for release team decision on MySQL and MariaDB [was: Re: Bug#793316: Bug#793316: transition: mysql-5.6]

[Robie Basak]

On Mon, Jan 11, 2016 at 02:52:26PM +0100, Pedretti Fabio wrote:
>  Note however that for other debian packaged softwares a choice was made,
> here are some I just remember:
> - openoffice / libreoffice
> - xfree86 / xorg
> - libav / ffmpeg

This is a valid point, but is the situation really comparable here?

With MySQL and MariaDB we are in a situation where the maintainer (team)
wants to maintain both (and is doing so). A release team decision that
picks one would be forcing the maintainer to choose. Has this ever
happened before?

> Actually mariadb and mysql can be used as alternative, but what should do
> in the future packages depending on them when they'll start to diverge?
> Specify just one of them as an explicit requirement? But then some packages
> depending on one cannot be installed along packages depending on the other
> because mariadb and mysql cannot installed at the same time?
> Or just use a set of common features compatible with both, possibly being
> unoptimal with both? And which one should users install?
> 
> I think that in the interest of Debian a choice should be made, as it was
> recently made with the libav / ffmpeg alternatives. Also other distros
> already did a choice. Users needing the other can still install from a 3rd
> party repository.

Why would this be in the interest of Debian? Surely users will be better
served by being given a choice? Why is it a problem for users for your
3rd party repository to be able to get those packages from inside Debian
instead?

I think this is quite different from ffmpeg because having both isn't
really giving users choice, since things will have been built against
one or the other. This doesn't really apply to MySQL vs. MariaDB because
the primary thing we ship is a server daemon and not a library.

(I'm setting aside concerns about maintenance burden for developers
outside the Debian MySQL maintainer team like the security team because
while the concerns are valid if left unaddressed, they aren't relevant
to a discussion about what would be best for users).

Robie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-mysql-maint/attachments/20160111/7a992a64/attachment.sig>