Closed GoogleCodeExporter closed 8 years ago
Already discussed that on mail with CryHam. We decided to make a second
repository. Here's the link, although no content yet:
http://code.google.com/p/vdrift-ogre/source/list?repo=data
Original comment by scrawl...@gmail.com
on 20 Mar 2011 at 10:51
[deleted comment]
Yes, let me put here my point of view.
The code repo should be best for quick getting the latest version for build. It
will grow
bigger because of commits and so. But if I'd put there data too it certainly
would slow down. So let's keep it for code and materials, scripts and such
things that can be edited from time to time (they are associated with source
somehow, wrong material can crash on other code). hg gets the whole repo with
history so I guess it would get slow soon with all data.
So I'm definitely not for 1st option (having data and source in 1 repo). I kind
of like the 2nd option with minimal data, but the third is the best for me
(separate repo's for code,data and tracks (or just for data ?)).
One thing is speed - we need fast pushes and pulls, hg doesn't have to check
all textures and tracks and so, when pushing code (I can't imagine hg doing it
fast).
Second thing is space - we have releases containing data, currently it is so:
534 MB (13% of total quota) = 4.8 MB Source + 530 MB Download.
And third - many people probably want to get the game (not 150MB only 60MB) to
see how is it the gameplay and don't want to download much, unpack it (and know
where), or certainly don't know how to use repo to get data (that for are full
game releases with 5 tracks or so). Some of them could use more tracks if they
like the game (but still don't want to use repo).
Downloads can be deleted. I don't know, but big data from repo cannot (am I
right ?).
I'm also thinking that it would be good to put full releases and track packs in
SourceForge, so we could have data repo and everything newest here. Is it the
best option ? What do you think ?
And finally at some distant future it would be great if the game itself could
download more tracks from repo (guys from VDrift are implementing this for
svn). Thus I like the option of tracks being a 3rd repo.
Original comment by Cry...@gmail.com
on 20 Mar 2011 at 11:40
As discussed in IRC, there is now 3 repositories, all containing files.
Compiling guide is also updated. Closing.
Original comment by tapiovie...@gmail.com
on 20 Mar 2011 at 3:03
Original issue reported on code.google.com by
tapiovie...@gmail.com
on 20 Mar 2011 at 10:00