|Good VCS for a Marathon scenario?|
|Posted By: Forrest of B.org||Date: 8/30/13 2:46 p.m.|
So as my last few questions may have hinted at, I'm looking to release a new version of Eternal soon; what would have been 1.1b4 if life hadn't suddenly taken a shit on me at the end of 2009, which has a lot of things that other people have contributed to the project that I haven't even had time to playtest properly until life finally settled down recently.
I'm hoping to put that release, along with all the source files (the PSDs, etc, that the game content is made from; not source code), up on a version control system of some sort so that the Marathon community at large can make improvements to it as they feel like without myself being a bottleneck on the process anymore.
I was initially planning on using GitHub because I'm familiar with git and because GitHub has a really friendly GUI interface so ever Marathoners with no real development experience can pick it up pretty easily.
But apparently GitHub doesn't like repos over 1GB, and Eternal with all of its source files is about 2.5GB. Plus apparently git itself is not fond of large binary files, which many of the source files are, and all of the actual Marathon files (Shapes, etc) are.
Does anyone have any recommendations on some kind of version control system that would be amenable to a Marathon scenario project?
|Good VCS for a Marathon scenario?||Forrest of B.org||8/30/13 2:46 p.m.|
|Re: Good VCS for a Marathon scenario?||treellama||9/4/13 3:48 a.m.|
Problems? Suggestions? Comments? Email firstname.lastname@example.org
Marathon's Story Forum is maintained with WebBBS 5.12.