[debian-mysql] factoring out mysql-common

[Andreas Beckmann]

On 2016-06-14 12:55, Robie Basak wrote:
> On Thu, Jun 09, 2016 at 12:51:06PM +0300, Otto Kekäläinen wrote:
>> I've set up http://anonscm.debian.org/cgit/pkg-mysql/mysql-defaults.git/

> 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.

Interesting approach, let me think about it ...

> Second, can we start keeping things in a single git repo rather than
> creating yet another one? How about we continue to use mysql-5.7 but
> have a "common" branch? Then eventually perhaps we can move mariadb into
> the same git tree too.

That would require a well defined scheme for naming branches and tags.
DEP14 comes into my mind (http://dep.debian.net/deps/dep14/), but it
needs an additional level for the source package, what do you think about

Upstream branches:
   <package>/upstream
Upstream tags:
   <package>/upstream/<version>

Master branches:
   <package>/<vendor>/master
   (maybe just <package>/master)
Release branches:
   <package>/<vendor>/<codename>
Tags:
   <package>/<vendor>/<version>

User branches:
   <user>/<whatever>
User tags:
   None

"Merging" the repositories should work as well if we rename the branches
first. I don't expect collisions in the tags (but the tags will be
cluttered since it is not clear which package they belong to), but we
can't rename tags (especially signed ones).


So src:mysql-defaults could live in

  mysql-defaults/master

tagged as

  mysql-defaults/debian/<version>

and in case you need to do modifications for Ubuntu, you could create

  mysql-defaults/ubuntu/master

tagged as

mysql-defaults/ubuntu/<version>


Andreas