Tux:HOWTO Subversion
From ArdekanturWiki
Contents |
[edit] HOWTO: Subversion on Tux
This information is highly arbitrary and designed to tiptoe around the fact that Tux is not made for Subversion at the moment. Eventually a simple interface will be provided that allows on the fly creation, removal, and activation of repositories.
[edit] Preparing for Subversion
- Create a directory hierarchy for your Subversion repositories.
~/svn/repos/<your id>is recommended. The use of your user-id is to prevent conflicting namespaces.
[edit] Creating a repository
- Think of a succinct name for your project. For example, if you are working on Part 1 of Assignment 2 of your CS360 homework, your repository name could be
cs360-assgn2-part1. This is a perfectly valid repository name. - Create the subversion repository:
svnadmin create ~/svn/repos/<your id>/<project name>. If all goes well there will be no output. - Create a temporary directory for your files:
mkdir -p ~/tmp/<project name>. Move all the files you want to be in the initial import of the project into this directory, or create them there. It is recommended you create a small README file to ensure you can see if the Subversion works. - Stay in the temporary directory, and import the temporary location into the subversion repository:
svn import file:///home/<your id>/svn/repos/<your id>/<project name> . -m "initial import". The-mflag tells Subversion what the upload message is for this import. If all goes well, then you will get a message saying that you've committed the first revision.
[edit] Running the Subversion Listener
- SSH into tux and find out what node of tux you are on. You can do this by typing
uname -aat your prompt. Remember this name, as you will need it to call the server when you checkout locally. - Start the Subversion listener:
svnserve -r ~/svn/repos -d. The-dflag will tell the listener to start as a daemon, and the-rflag will tell the listener to not allow anyone to access any files above your repository directory.
