Difference between revisions of "MG/Getting The Code"
(Adding categories) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | ''' | + | '''NOTE: Due to problems converting to Git, MegaGlest is still using SVN.''' |
| − | + | <!-- REMOVE THIS LINE WHEN CONVERTED TO GIT | |
| − | |||
[[MegaGlest]] has now switched to git for managing the game's source code and data (the svn repo is no longer active). Using the command line you would get the code in one of two ways. Either read-only if you will not contribute changes or read and write if you plan to help contribute to the project as well. | [[MegaGlest]] has now switched to git for managing the game's source code and data (the svn repo is no longer active). Using the command line you would get the code in one of two ways. Either read-only if you will not contribute changes or read and write if you plan to help contribute to the project as well. | ||
| Line 41: | Line 40: | ||
git://megaglest.git.sourceforge.net/gitroot/megaglest/megaglest /megaglest-data | git://megaglest.git.sourceforge.net/gitroot/megaglest/megaglest /megaglest-data | ||
git://megaglest.git.sourceforge.net/gitroot/megaglest/megaglest /megaglest-data-source | git://megaglest.git.sourceforge.net/gitroot/megaglest/megaglest /megaglest-data-source | ||
| + | REMOVE THIS LINE WHEN CONVERTED TO GIT --> | ||
==SVN== | ==SVN== | ||
| Line 59: | Line 59: | ||
*[[MG/SVN Structure|SVN Structure]] | *[[MG/SVN Structure|SVN Structure]] | ||
[[Category:MG]] | [[Category:MG]] | ||
| + | [[Category:Cate Everett2]] | ||
Revision as of 17:12, 11 February 2012
NOTE: Due to problems converting to Git, MegaGlest is still using SVN.
SVN
The SVN section is now deprecated, but will work for version 3.6.0.2 and earlier.
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.