[Scummvm-devel] ATTN: Proposed layout for git repository
Eugene Sandulenko
sev at scummvm.org
Sun Sep 23 20:37:06 CEST 2012
On 23 September 2012 21:15, Johannes Schickel <lordhoto at gmail.com> wrote:
> Last but not least the differentation between "web" and "sites". I think all
> are bascially "sites".
So, the current situation is this:
No arguments:
docs/trunk/docbook --> /dev/null
engine-data/tags/* --> /dev/null
scummex/* --> scummex (??? it will go first in the list, but
scummvm-scummex looks weird to me)
media/* --> scummvm-media
I would like to keep -vendor, and keep original sources there which we
have permissions for redistribution. Such as original dreamweb code,
and as I remember, Lure.
vendor --> scummvm-vendor
Now on the websites:
Right, keeping them in subdirectories makes it tricky to autoupdate on
the target sites. So let's ditch that.
Option 1. Separate repo for everything
buildbot --> scummvm-buildbot
doxygen --> scummvm-doxygen
forum/trunk --> scummvm-forum
web/* --> scummvm-web
web-planet -- scummvm-planet
wiki/trunk -- scummvm-wiki
Option 2. Put everything in branches on scummvm-sites.
buildbot -> scummvm-sites:buildbot
doxygen --> scummvm-sites:doxygen
forum/trunk --> scummvm-sites:forum
web/* --> scummvm-sites:master ??
web-planet -- scummvm-sites:planet
wiki/trunk -- scummvm-sites:wiki
The problem with this option is that you have to pull everything for
modifying just the buildbot scripts. Currently it takes about 350MB
for -web repo. I'd say that's a lot. This was my primary reason why I
proposed to put it into a separate repository.
Option 3. Web separate in scummvm-web, rest is in branches on
scummvm-sites or scummvm-web-other.
Thoughts?
Eugene
More information about the Scummvm-devel
mailing list