[debian-mysql] Future general packaging improvements [was: Re: Bug#792080: mysql-common: needs to handle upgrades from mariadb-common that creates my.cnf -> mariadb.cnf symlink]

[Otto Kekäläinen]

2015-07-17 14:30 GMT+03:00 Robie Basak <robie.basak at ubuntu.com>:
> (replaced Cc: bug with Cc: ML)
>
> On Fri, Jul 17, 2015 at 01:10:35PM +0200, Andreas Beckmann wrote:
>> And now we are moving slightly offtopic in this bug:
>>
>> * Have you considered building mysql-common from a separate source
>> package? Because since it is a required part for all mysql compatible
>> stuff it shouldn't be blocked by being bundled to a specific
>> implementation that is temporarily not being "ready for migration"
>
> We have mentioned it, yes, and I'm happy for that to happen. I'd like to
> take one step at a time, though, so I'd like to have the current
> situation resolved and both mysql-5.6 and mariadb-10.0 in testing with
> no outstanding bugs related to the changes we've made already first.
> Then it should just be a case of pulling it out, right?

Anticipating that it will take some time for mysql-5.6 to pass from
unstable to testing successfully, and as the mysql-common 5.6
dependency in mariadb will block new mariadb versions from entering to
testing for a long time, I would be favour in making the mysql-common
a separate source package rather sooner than later.

Andreas: as the pkg-mysql-team is rather short on contributors, could
you please stay around and also help out by making the mysql-common a
separate new source package?

- Otto