Welcome to the GiPSi Development Wiki
Wiki Contents
- Repository Usage Guidelines (this page)
- Repository Structure Page
Introduction to Subversion
The GiPSi source-code is now stored in a Subversion repository. For those who have used CVS in the past, Subversion is designed to be very similiar in operation. Subversion command line clients are available for most unices, Mac OS X, and Cygwin environments. There are also several good graphical Subversion clients such as TortoiseSVN (http://tortoisesvn.tigris.org/). A good reference to subversion that is geared towards the command line, but is also very useful if you use Tortoise, is available at http://svnbook.red-bean.com/en/1.1/index.html.
Subversion is a source-code repository with version control. It's primary function is to organize and track changes to a source tree being modified by multiple users. The first step in interacting with the repository is to 'Check-out' the latest version. There are several branches of the source tree in the repository; for this example, we want to download the main internal development version, referred to as the 'trunk' branch. If you are using TortoiseSVN, right click on the folder and select the "SVN Checkout" option. The URL of the repository is http://reducto.cwru.edu/svn/gipsi/trunk.
After this step, the SVN client will download the latest version of the trunk branch and make a local copy of it on your harddrive. You can now make changes to these files. When you make changes, if you have TortoiseSVN installed, it will put a red exclaimation point icon on the file icon to show that you've modified it. You can request to see the differences between your version and the current version by right clicking on the file and selecting the "Diff" option from the TortoiseSVN menu. TortoiseSVN Diff supports text files and word documents.
Before you commit any changes back to the SVN Repository, consider that the trunk branch is the latest shared development version of the source tree. You shouldn't commit any changes to the trunk branch unless you're sure it's okay with Prof. Cavusoglu or Prof. Liberatore. In the meantime, you can still use the SVN repository to share your changes and backup of your code, but you'll want to do it in your own private branch. To make a new branch, checkout a fresh version of 'trunk' as described above, and then right click on the checked-out folder and select "Branch/Tag". A dialog box will ask you for the URL of the branch you wish to create. The repository is set up like this:
- Trunk
- Releases
- 1.0.1
