An SVN Re-arrangement
Moderator: Moderators
An SVN Re-arrangement
I propose that all lobby related projects be re-arranged into a /lobby/ subfolder, including unitsync, TASServer, TASClient, AFLobby, Springie, UnityLobby, the old C# lobby and Omni.
It would make /trunk look cleaner, and thus easier to navigate, reconciling 5 root folders into 1.
It would make /trunk look cleaner, and thus easier to navigate, reconciling 5 root folders into 1.
-
- Spring Developer
- Posts: 1254
- Joined: 24 Jun 2007, 08:34
- Tim Blokdijk
- Posts: 1242
- Joined: 29 May 2005, 11:18
I suggest that everything necessary to compile and install the game itself is moved into a subdirectory called something like Game.
This means the following dirs and files:
AI Documentation Doxyfile game installer LICENSE.html lua README.html README.MACOSX.txt rts SConstruct tools/unitsync
Then as AF suggested, another folder Lobby, which contains:
AFLobby omni TASClient TASServer UnityLobby
This would leave trunk with the following dirs:
Game Lobby Site
and these stray thingies which I couldn't place properly:
backup (who needs a dir called backup in a version control system anyway), crashrpt (perhaps this should be in tools/ or libs/ or sth like that), tools (might be renamed Tools and kept in trunk/), and directories.txt which seems to belong there.
This would have the benefit that if you want to download and install the game itself, you only need to checkout trunk/Game and even more so for automated svn installers that do this for you, which would reduce the burden on both the svn server and the user, and make the relevant source tarballs smaller.
.
Not much point in moving Site dir, as it's already in toplevel, and moving it deeper would not make it easier to leave it out of checkout when not needed/desired.
Oh and when you want to update your spring trunk/ without getting any Site updates, do this (works at least in bash):
My proposed changes would in effect make the common case svn checkout be one third of the original size in MB.
This means the following dirs and files:
AI Documentation Doxyfile game installer LICENSE.html lua README.html README.MACOSX.txt rts SConstruct tools/unitsync
Then as AF suggested, another folder Lobby, which contains:
AFLobby omni TASClient TASServer UnityLobby
This would leave trunk with the following dirs:
Game Lobby Site
and these stray thingies which I couldn't place properly:
backup (who needs a dir called backup in a version control system anyway), crashrpt (perhaps this should be in tools/ or libs/ or sth like that), tools (might be renamed Tools and kept in trunk/), and directories.txt which seems to belong there.
This would have the benefit that if you want to download and install the game itself, you only need to checkout trunk/Game and even more so for automated svn installers that do this for you, which would reduce the burden on both the svn server and the user, and make the relevant source tarballs smaller.
.
Not much point in moving Site dir, as it's already in toplevel, and moving it deeper would not make it easier to leave it out of checkout when not needed/desired.
Oh and when you want to update your spring trunk/ without getting any Site updates, do this (works at least in bash):
Code: Select all
svn up $(ls -I Site)
- Tim Blokdijk
- Posts: 1242
- Joined: 29 May 2005, 11:18
Basically I agree, not sure about all change though, but the following should be fine as first step:
- trunk/Lobby/ with TASServer, TASClient, AFLobby, UnityLobby, backup/SomeLobbies and maybe some other stuff in it (may need to drag in the more recent UnityLobby code from hollowsoul's own SVN to make it truely useful to keep it alive there).
Note that I don't think it is a good idea to put unitsync there because unitsync needs to be compiled and depends on Spring source files, so it isn't truely a separate project. - In an Engine directory:
- Engine/src directory containing current rts and tools/unitsync and other tools with a heavy source code dependency on the engine (none at this moment, I think, but a unitsync V2 may be written some time..., or a stand alone game server using same server code as engine, etc.)
- Engine/game
- Engine/installer
- Engine/Documentation
- and the files: Doxyfile, LICSENSE.html, README.html, README.MACOSX.txt, SConstruct