Subversion Repository

General Connection Details

  • Repository URL: http://svn1.cvsdude.com/modius/farcry
  • Read only anonymous access available

The FarCry repository follows a standard best practice layout for version control with a trunk, branches and tags. You need to make sure you check out each module and its corresponding branch/tag independently ie. don't try and checkout the entire /farcry repository onto your environment.

farcry_core (module)

  • trunk
    (the very latest cutting edge code; please don't cry if it wreaks chaos and destruction throughout your implementation)
  • branches
    p300 (3.0.x maintenance branch)
    p230 (2.3.x maintenance branch)
  • tags
    milestone_3-0-1
    approved milestone releases (use these in production)

To grab a specific maintenance branch of farcry_core such as p300 you'd use the following URL:

  • http://svn1.cvsdude.com/modius/farcry/farcry_core/branches/p300
  • to check out code to ./farcry_core

To grab a specific milestone release (good for production environments and also available as a complete ZIP file) you might use:

  • http://svn1.cvsdude.com/modius/farcry/farcry_core/tags/milestone_3-0-1
  • to check out code to ./farcry_core
Both of these examples should be checked out to a local folder on your system with the name ./farcry_core -- this is important. If you are use to CVS you might be inclined to check out branch p300 into a folder called p300 -- but instead you are checking out p300 to a folder called ./farcry_core. Hopefully that's not confused you entirely :)

fourq (module)

  • trunk
  • branches
    p300 (maintenance branch for use with farcry_core p300 branch)
  • tags

farcry_mollio (module)

  • trunk
  • branches
  • tags

 

 

FarCry - Mollio