SVN Index
SVN Crossfire Repository
On 2006-Sept-19, Crossfire migrated from CVS to SVN - which was chosen due to desired key features that were voted upon via the mailing list and the wiki.
More details and information to follow, when available.
SVN Information
General Commands:
The general commands to check out a module (archtypes, client, maps, server map editor, et al) is the following:
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/client
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps
- svn co https://svn.sourceforge.net/svnroot/gridarta
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/server
Note: More information is available in regards to Gridarta SVN repository and development status.
Trunk & Branch:
You will also notice that there are directories labaled as trunk and branch.
The trunk is the latest development changes going only into 2.0 when it is released.
The 1.x branch is for continued 1.x development, including only small bugfixes and minor features.
Unless doing development it is recommended to use the 1.x branch until 2.0 is released.
- Development , recent updates and latest features == trunk
- Tested & stable features, bug fixes, etc. == branch
Notice: It is highly recommend that you use a trunk mapset with a trunk server and a branch mapset with a branch server as incompatable changes may occur. Meaning a map in trunk may only work with the trunk server and vice versa.
Trunk & Branch Commands:
The commands to check out a specific directory is the following:
Note: The commands, below, presume you are in the directory where the archetypes, client, maps or server currently reside.
- Branch:
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/branches/1.x
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/branches/1.x
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/branches/1.x
- Trunk:
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/arch/trunk
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/client/trunk
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/trunk
- svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/server/trunk
It is also possible to checkout files from SVN and have them install to a remote directory. This is accomplished by adding the file path to the end of the SVN command.
For instance:
svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x /path/to/map/directory/
Or, more specifically:
svn co https://crossfire.svn.sourceforge.net/svnroot/crossfire/maps/branches/1.x /share/crossfire/maps/
This would check out the latest changes to maps 1.x branch and place them in the /share/crossfire/maps/ directory.
Browse the SVN Repository
Latest SVN changes and history is availble at: http://crossfire.svn.sourceforge.net/viewvc/crossfire/
Building from Source - Notes
When building the server from source, make sure you have the arch section which contains the archetypes, and symlink lib/arch in the server tree to that.
This means that for trunk you use :
cd lib
ln -s ../../arch/trunk arch
And for 1.x this means :
cd lib
ln -s ../../../arch/branches/1.x arch
Btw, one note about using trunk, is that trunk is for 2.x work right now, and though hasn't happened yet, it's likely that the trunk client will remove support for 1.x servers and the trunk server will remove support for 1.x clients, at some point. The 1.x branch is about just as actively maintained as trunk and most changes lately go into both, so unless you're planning on doing development (or at a later date using a 2.x client to playtest changes on a 2.x balance testing server (if/when we have one of those)), you'd be best off using the 1.x branch as opposed to trunk.
Thanks Rednaxela ! - http://forum.metalforge.net/viewtopic.php?t=1627
