Subversion Access

Table of Contents

Subversion Access 
Subversion is able to cache passwords 
Subversion password management 
Working with Subversion Commands: How To 
Where Is My Working Copy? 
Adding New Files to the Repository 
How to Propagate Changes to the Repository 
How to Create Baselines 
How to Work in Isolation 

Subversion Access

In order to avoid a certain bug, or for any reason, you might want to get the tovid from latest svn subversion. Believe me, it is as simple as ABC:

  1. decide where you want store you subversion files.
  2. mkdir/cd into it.
  3. issue the svn command to check it out.

    $ cd /export/repositories/svnwork
    $ svn co tovid
    A    tovid/trunk
    A    tovid/trunk/tovid
    A    tovid/trunk/tovid/AUTHORS
    A    tovid/trunk/tovid/ChangeLog
    A    tovid/branches/tovid-pycairo/py-compile
    Checked out revision 1507.

That's it. You've get the latest tovid from svn subversion!

I'm running Debian Testing, the only package I need to install for above is

subversion  Advanced version control system

That's seems to be the most hassle free solution to me, but if you still prefer GUI version, I believe there are lots of solutions also. Here is a few from my Debian list:

esvn - frontend for the Subversion revision system written in Qt
gforge-plugin-scmsvn - subversion plugin for GForge
kdesvn - subversion client with tight KDE integration
python-svn - A(nother) Python interface to Subversion
rapidsvn - A GUI client for subversion
websvn - interface for subversion repositories written in PHP

For more on Version Control using Subversion, check out

also lists a few subversion GUI tools, as well as explaining the basics of subversion.



documented on: 2006-12-19

Subversion is able to cache passwords 

Note that subversion is able to cache passwords:

First issuing svn:

$ svn commit --username=suntong001 --message "Enable using ttf font file as -font" trunk/tovid/src/makemenu
Password for 'suntong001':
Sending        trunk/tovid/src/makemenu

Succeeding svn:

$ svn commit --username=suntong001 --message "Make menu selection looks more comfortable when -align right" trunk/tovid/src/makemenu
Sending        trunk/tovid/src/makemenu

I.e., no password asked any more.

documented on: 2006-12-19

Subversion password management 

Client Credentials Caching

Many servers are configured to require authentication on every request. This would be a big annoyance to users, if they were forced to type their passwords over and over again. Fortunately, the Subversion client has a remedy for this — a built-in system for caching authentication credentials on disk. By default, whenever the command-line client successfully responds to a server's authentication challenge, it saves the credentials in the user's private runtime configuration area (~/.subversion/auth/ on Unix-like systems or %APPDATA%/Subversion/auth/ on Windows; see the section called "Runtime Configuration Area" for more details about the runtime configuration system). Successful credentials are cached on disk, keyed on a combination of the server's hostname, port, and authentication realm.

When the client receives an authentication challenge, it first looks for the appropriate credentials in the user's disk cache. If seemingly suitable credentials are not present, or if the cached credentials ultimately fail to authenticate, then the client will, by default, fall back to prompting the user for the necessary information.

documented on: 2008-03-22