Strict Standards: Declaration of Doku_Renderer_metadata::table_open() should be compatible with Doku_Renderer::table_open($maxcols = NULL, $numrows = NULL, $pos = NULL) in /home2/cp-wiki/htdocs/inc/parser/metadata.php on line 480

Strict Standards: Declaration of Doku_Renderer_metadata::table_close() should be compatible with Doku_Renderer::table_close($pos = NULL) in /home2/cp-wiki/htdocs/inc/parser/metadata.php on line 480

Using Subversion for SECANT Projects

A SECANT project repository is available using Subversion (svn) at secant.cs.purdue.edu. This page explains how project members should use it. See this page for setup and administrative information.

This page is primarily for UNIX users. Windows instructions are here.

Creating an SSH Key for Access to the Repository

On a UNIX system, use ssh-keygen to create a public/private key pair. Give it a SECANT-specific name (to distinguish it from any other ssh keys you may have) and store it in the default directory (~/.ssh):

% ssh-keygen -t rsa -f ~/.ssh/id_rsa_secant

ssh-keygen will prompt you for a passphrase to lock the key. This protection is not necessary; you can skip it by pressing ENTER twice. ssh-keygen will create two files in your ~/.ssh directory, with the private key in id_rsa_secant and the public key in id_rsa_secant.pub.

Send me a copy of your public key file, id_rsa_secant.pub. I will then create an svn account for you and tie your public key to that account.

Setting Up Your Working Environment for Repository Access

While waiting for me to create your svn account, you can read the svn tour or other documentation and set up your UNIX environment for svn access.

If you're only dealing with this one repository (i.e., you're not involved in any other projects that use svn), then it is simplest to just set the SVN_SSH environment variable to turn on ssh key access and log you in to the cp-wiki account. For example, bash users edit ~/.bashrc to include:

SVN_SSH="ssh -i $HOME/.ssh/id_rsa_secant -l cp-wiki"
export SVN_SSH

Once your svn account is created, cd to a suitable directory and get a copy of the repository:

% cd secant
% svn checkout svn+ssh://secant.cs.purdue.edu repository

These commands move into your secant directory and create a repository subdirectory with a complete copy of the SECANT source code repository. The repository is organized as recommended by the svn community: one directory per “project”, with each project containing a branches, tags, and trunk subdirectory. You'll notice that the repository directory contains two subdirectories: skeletons for “project1” and “project2”. The main place to create files (e.g., python source code) is in the trunk directory. Start there.

Creating a New Project

The basic steps for adding a new project are to start in the repository directory, make sure you are up-to-date, create the directory structure, add to the project, then commit:

% cd repository
% svn update
% mkdir project3 project3/branches project3/tags project3/trunk
% svn add project3
% svn commit

Create your first file(s) in project3/trunk.

 
svn.txt · Last modified: 2008/01/11 14:51 by jtk
 
Recent changes RSS feed Creative Commons License Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki