Mark de Wever <[email protected]>: > We already know it will be more than 1 GB, as stated before AI tested > and ended with a 1.4 GiB repo.
Yes, but git-svn makes some design choices that I think might result might result in blob duplication. We have enough really large blobs to make this an issue. I am now pretty confident that I'll be able to load the whole thing, by the way. I'm at about r10K of about 144K with only about 1% of the available volume used up. Somehow I had it in my head that we were into TB range, not GB. > > I think the targets for being split out are, in this order: > > > > 1. Translations > > 2. Audio > > 3. Graphics. > > Before considering splitting I like to know how it affects the work-flow > for the developers, translators and the release manager. See https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial for a tutorial on how all this works. Splitting out translations would be pretty low impact, since (as others have pointed out) Wesnoth runs fine without them. Developers would barely notice. Translators would have an extra git update step to do after pulling, then have to run git push from within the translation repo rather than the main one. The release manager would also have one extra git update step. For audio, pretty similar, except subsitute "composer" for "translator". The key point in common with translations is that all the stuff we'd want to isolate into a submodule is in one subdirectory. That makes it easy. Isolating out graphics would be much messier, since those resources are spread out across many directories. I now think this is probably not a good idea. Better to break out the resource branch; in fact, that should probably be done first. -- <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
