[Issue 11792] Investigate migrating to a meta repo

[d-bugmail at puremagic.com]

https://d.puremagic.com/issues/show_bug.cgi?id=11792


Mathias LANG <pro.mathias.lang at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pro.mathias.lang at gmail.com


--- Comment #2 from Mathias LANG <pro.mathias.lang at gmail.com> 2014-01-03 19:01:53 PST ---
That's simple to setup but tedious to use.
I made some tests in https://github.com/Geod24/MetaD
This is my feedback:

1) Starting from 1.8.2, git can track a branch, not only a commit. When you
checkout it's still set to a specific commit though, you need to pass the
`--remote` option to `git submodule update`
So I think we could make the repo point to the latest release, and our
contributor just need to keep in mind to passe `--remote`. This design void the
necessity of a hook.

2) I was wondering what the workflow would be with submodules.
I'm currently still testing and updating the README accordingly.
The most annoyance so far is that submodule HEAD gets detached quite easily.
The other problem is that your repository gets "dirty" by using --remote. I
think we should try to lower the need of git submodule commands, as using them
is tricky and often leads to confusion, like commiting in the wrong order. We
should also take care not to accept a PR with a modif to .gitmodules unless
it's a stable version update.

3) I'll take a look at the merging strategy soon. By default submodules are
just binary object, but git provide a way to merge/rebase them too as part of
the update process.

I'll keep experimenting with it, any comment / example of your normal workflow
is very welcome.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------