Re: About packages that depend on mysql-* / mariadb / virtual-mysql-*
Hi,
On 11/04/16 22:38, Otto Kekäläinen wrote:
> 1. MariaDB as default
>
> We shall not invent a new metapackage, but instead leverage on the
> existing virtual-mysql-server/cllient package scheme. It was agreed
> upon already back in 2013 and all upstreams and downstreams to date
> follow the convention (including MariaDB, Percona, Oracle and even
> mysql-wsrep). This scheme is both backwards compatible and future
> proof if users combine vanilla Debian repositories with external
> repositories. Using the existing scheme requries least effort to
> extend, and as it involves least amount of change it is technically
> also least risky in terms of regressions or other problems.
>
> As so, we now propose to mass file bugs about packages in Debian that
> currently depend on mysql-* to depend on mariadb-* | virtual-mysql-*
> instead. If nobody objects, I'll write about the intent to mass file
> bug to debian-devel in a few days and then actually file the bugs in
> 1-2 weeks.
>
> I have already documented it here:
> https://wiki.debian.org/Teams/MySQL/virtual-mysql-server
Any progress on this? Have you already filed bugs?
> 2. mysql-common and configuration
>
> Both packages mysql-5.6 and mariadb-10.0 use mysql-common from
> mysql-5.6. It will be split into a separate source package that is
> independent of the mysql-5.6 source package (or any later version).
>
> Andreas B: Can you make an action point to yourself about issue 2? It
> would help a lot if I am not alone responsible of implementing all
> requested changes.
I guess this is still pending?
> 3. libmysqlclient.so.18
>
> The pkg-mysql-maint team will continue to discuss this issue and get
> back later with a suggestion on how to do it.
Any update on this?
Thanks,
Emilio
Reply to: