1. Create repository:
Subversion provides two options for the type of underlying data store that each repository uses.
See the comparison in
here or
http://svnbook.org/shell> mkdir /home/svn/repos
shell> svnadmin create --fs-type fsfs /home/svn/repos
The Subversion Repository, Defined in
hereconf
A directory containing repository configuration files.
dav
A directory provided to mod_dav_svn for its private housekeeping data.
db
The data store for all of your versioned data.
format
A file that contains a single integer that indicates the version number of the repository layout.
hooks
A directory full of hook script templates (and hook scripts themselves, once you've installed some).
locks
A directory for Subversion's repository lock files, used for tracking accessors to the repository.
README.txt
A file whose contents merely inform its readers that they are looking at a Subversion repository.
2. Import data:
See the
"Planning Your Repository Organization" to decide how to organize your projects with respect to repositories.
Your first decision is whether to use a single repository for multiple projects, or to give each project its own repository, or some compromise of these two.
shell> svn import /home/svn/tmp/ file:///home/svn/repos/ -m "Initial Import"
3. Show repository:
shell> svn list -v file:///home/svn/repos/
shell> svnlook info --revision 1 /home/svn/repos/
shell> svnlook tree /home/svn/repos/ --show-ids
4. Invoking server
shell> svnserve -d --listen-port 3690 -r /home/svn
Reference:
http://www-128.ibm.com/developerworks/cn/java/j-lo-apache-subversion/index.htmlhttp://svnbook.red-bean.com/en/1.4/index.html
