[debian-mysql] factoring out mysql-common (+mysql.git branch layout)

[Otto Kekäläinen]

Hello!

2016-06-14 16:56 GMT+03:00 Robie Basak <robie.basak at ubuntu.com>:
> On Tue, Jun 14, 2016 at 04:26:25PM +0300, Otto Kekäläinen wrote:
>> 2016-06-14 14:58 GMT+03:00 Andreas Beckmann <anbe at debian.org>:
>> >> I've just looked at this now. I'm disappointed that the history is lost.
>> >> Can we instead base this tree from mysql-5.7's tree - just strip out
>> >> everything not wanted in a branch, and refactor the remaining into a
>> >> mysql-common? Then "git blame" etc will still work.
>>
>> I don't mind either way. Git blame will anyway not go beyond mysql-5.5
>> contents, but at least we would have the history for the last couple
>> of years and maybe indeed the majority of changes to mysql-common
>> contents was done in recent years. If Andreas or Robie wants to
>> refactor the mysql-common repo to be based on the mysql-5.7 repo,
>> please do it.
>
> Great, thanks. Andreas, shall I leave this to you? Or if you'd like me
> to do it, I'd be happy to push my result somewhere, but I'll need a DD
> to clean up the repos when I'm done (since AIUI I can't force push to
> Alioth).

Andreas stated that he does not have time. So please Robie implement
this if you want. I can then help with upload to Alioth in case
something special is required.

We will have a mysql/mariadb packaging session here at DebConf on
Tuesday. Is there any chance you can do this by then, so that future
developments can build directly on the new repo layout? I hope to
attract some new contributors during that session etc.

The latest version of the refactored mysql-common package is at
http://anonscm.debian.org/cgit/pkg-mysql/mysql-defaults.git/ -> Please
Robie follow it to create the mysql-defaults branch. The contents has
been reviewed and accepted for the mysql-defaults package part (but
default-mysql-* part is still open to discussion).

[..branch layout proposal..]
>
> I would be happy with this. In fact this would be much better than the
> current situation, where jumping around and asking for diffs, etc
> between MySQL 5.5, 5.6 and 5.7, eg. for security updates, has been quite
> painful because all the branch names collide.

Great, then Robie please proceed.