(Clarification) |
(→SVN) |
||
| Line 45: | Line 45: | ||
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: |
||
| − | <pre>svn co https:// |
+ | <pre>svn co https://svn.code.sf.net/p/megaglest/code/trunk megaglest</pre> |
This will download to the current active folder, so be sure to first navigate to the folder you want to download the SVN into. |
This will download to the current active folder, so be sure to first navigate to the folder you want to download the SVN into. |
||
Revision as of 23:04, 7 November 2013
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://svn.code.sf.net/p/megaglest/code/trunk megaglest
This will download to the current active folder, so be sure to first navigate to the folder you want to download the SVN into.
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.