Re: Bug#732878: Add MariaDB as an alternative dependency
Excerpts from Thomas Goirand's message of 2013-12-27 00:36:49 -0800:
> On 12/27/2013 09:44 AM, Clint Byrum wrote:
> > Excerpts from Vincent Bernat's message of 2013-12-25 09:52:40 -0800:
> >> ❦ 25 décembre 2013 12:41 CET, Clint Byrum <spamaps@debian.org> :
> >>
> >>>>> Don't you think it would be more reasonable if the mariadb-client
> >>>>> contained a Provides: mysql-client, rather than changing each and every
> >>>>> software dependency in Debian?
> >>>>
> >>>> Maybe MariaDB wants to be the "default" MySQL implementation?
> >>>
> >>> MariaDB is not MySQL, so this is not really what you mean. Also I'd ask
> >>> that you suggest why you think there should be a default, and why you
> >>> think that "MySQL" should not be the default "MySQL".
> >>
> >> I am saying this because the bug reports about adding support for
> >> MariaDB were asking for mariadb-client | mysql-client and not
> >> mysql-client | mariadb-client. My question is genuine, I really don't
> >> know. Do we plan to transition away from MySQL to MariaDB?
> >
> > No such plan is under way. I am one of the few people maintaining MySQL,
> > but others have recently stepped up to get us onto git, to get MySQL
> > 5.6 ready, and to do general work, so MySQL seems like it may remain in
> > Debian. As long as it does, there is no "automatic transition". They are
> > forked, and more so than ever with MariaDB 10, so we should just treat
> > them as such.
>
> After all these replies, I'm still not sure what to do with my package.
> Should I add mariadb-client as possible dependency? If, like it seems,
> we get 4 different types of "MySQL compatible" servers (MySQL itself,
> MariaDB, and both with the Percona patch making Galera from MySQL or for
> MariaDB), does it makes sense to add dependency for all of them, in
> absolutely all the packages in the Debian archive?
>
> In other words, will I have to do something like:
> Depends: mysql-client | mariadb-client | mysql-galera-client |
> mariadb-galera-client
If we don't have a virtual-mysql-client that can guarantee a package
which provides /usr/bin/mysql as an alternative, then we should aim at that.
For you, mysql-client will work fine. You would only need mariadb-client
if you want to use a specific feature of mariadb-client. If they do
conflict/break/replace each-other (I can't remember if they do or not),
then you will need the "or" relationships until we provide you a proper
virtual package.
>
> or is the client for the galera and non-galera the same?
>
They all will speak mysql's network protocol, probably until the end of
time. I imagine some will add features.
Reply to: