Migration from CVS to SVN

This page contains notes related to GRASS code migration (planned) from CVS to SVN.

Basic

• The SVN command line interface is just like CVS, many tasks are identical - just change the program name from cvs to svn.

GRASS CVS repository structure

/grass-cvs
|
+---/grass
|
+---/grass51
|
+---/grass6
|
+---/grass_doc
|
+---/libgrass
|
+---/newsletter
|
+---/programgrass50
|
+---/web

GRASS OSGeo SVN repository structure

See Discussion page for details.

/grass-svn
|
+---/grass
|    |
|    +---/trunk (grass6 CVS HEAD)
|    |
|    +---/branches
|    |    |
|    |    +---/releasebranch_5_x (note: 5_5 based on grass5 CVS HEAD)
|    |    |
|    |    +---/releasebranch_6_x
|    |
|    +---/tags
|
|---/grass-addons
|
+---/grass-web
|    |
|    +---/trunk

Notes:

• grass51, grass_doc, libgrass and programgrass50 are dead, will be not migrated
• grass migrated as grass/branches/releasebranch_5_5
• web migrated as grass-web
• newsletter will be merged with OSGeo newsletter repository

Scripts:

./grass-cvs2svn-base.sh
./grass-cvs2svn-s2.sh
./grass-cvs2svn-wxpython.sh

→ grass-svn2

GRASS 7 development notes

External links

• My Experiences With Subversion by Simon Tatham
• cvs2svn tool page
• Migration plan example
• Converting CVS to subversion
• List CVS Tags

• Online book: Version Control with Subversion

SVN hosting

There are two main options to host the new SVN repository.