Difference between revisions of "MG/Getting The Code"
Jump to navigation
Jump to search
(Adding categories) |
(Remove misleading statement about this page being outdated for current versions. We have not yet switched to git..) |
||
| Line 43: | Line 43: | ||
==SVN== | ==SVN== | ||
| − | |||
If you chose a subversion CLI then run the following command to retrieve the latest source code: | If you chose a subversion CLI then run the following command to retrieve the latest source code: | ||
Revision as of 23:53, 4 April 2012
NOTE: Due to problems converting to Git, MegaGlest is still using SVN.
SVN
If you chose a subversion CLI then run the following command to retrieve the latest source code:
svn co https://megaglest.svn.sourceforge.net/svnroot/megaglest/trunk megaglest
Project folder layout
Tags and branches
This will check out the trunk directory, which is where active development takes place in. Each release is 'tagged' and a copy resides in the tags directory, so if you wanted an older release you would check out something below instead. Check here to see which ones are available.
Branches are created in the branches subdirectory when required to seperate larger changes from active / stable development, so replace 'trunk' by 'branches' and check with your web brower which ones are available if this is your intention.