Apache Subversion (often abbreviated SVN, after the command name svn) is a software versioning and revision control system distributed under an open source license. Developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS).
The open source community has used Subversion widely: for example in projects such as Apache Software Foundation, Free Pascal, FreeBSD, GCC, Mono and SourceForge. Google Code also provides Subversion hosting for their open source projects. BountySource systems use it exclusively. CodePlex offers access to Subversion as well as to other types of clients.
The corporate world has also started to adopt Subversion. A 2007 report by Forrester Research recognized Subversion as the sole leader in the Standalone Software Configuration Management (SCM) category and as a strong performer in the Software Configuration and Change Management (SCCM) category.[1]
Subversion was created by CollabNet Inc. in 2000 and is now a top-level Apache project being built and used by a global community of contributors.
Some of the commands frequently used related to SVN is listed below.
* Create Svn Repository
Syntax: svnadmin create <svn data directory><$repository_name>
E.g:
$ svnadmin create /var/www/svn/repotest-Command to create a repository using the default configuration.
$ chown apache.apache /var/www/svn/repotest– Command to use after creating the repository to assign ownership of the repository root directory to apache.
Or
Syntax: svnadmin create –fs-type fsfs <svn data directory><$repository_name>
$ svnadmin create --fs-type fsfs /var/www/svn/repotest-Command to create a repository using specifying the repository type.
$ chown apache.apache /var/www/svn/repotest– Command to use after creating the repository to assign ownership of the repository root directory to apache.
* Initially input repo data to repository
$ svn import -m "Initial import." /var/www/svn/repotest/ file:///var/www/svn/myrepo– where /var/www/svn/repotest / is the root directory of the repository and file:///var/www/svn/repotest will be the online repository directory
* list and view contents of a repo in tree view
Syntax: svnlook tree <repository absolute path>
$ svnlook tree /var/www/svn/repotest/
* View SVN Information
$ svn info
* List down all repo
$ svn st
* Add to svn a file or folder
$ svn add <file>
* Create a Directory for svn
$ svn mkdir <directory>
* Log svn
$ svn log
*To revert to original file
$ svn revert <path>
- revert a whole directory of files, use the --depth=infinity option:
$ svn revert --depth=infinity <path>
*Delete a file or directory from svn
$ svn delete <directory>
*Commit all changes made to file (Note: must be inside the repository path
$ svn ci -m "adding directories"
– Where ci is the commit command and -m is the parameter for the additional message and “adding directories” would be the notes included for the commit .
or
If you want to use a file that’s under version control for your commit message with --file, you need to pass the --force-log s witch:
$ svn commit --file file_under_vc.txt foo.c svn: The log message file is under version control svn: Log message file is a versioned file; use '--force-log' to override $ svn commit --force-log --file file_under_vc.txt foo.c Sending foo.c Transmitting file data . Committed revision 6.
*Checkout contents of Repository/get files and details
Syntax: svn co <repository_site> <path>
$ svn co http://svnrepo.com/svn/repos/ /var/www/svn/repotest/
For more commands on SVN Click here.
Happy versioning.
The Digital Metamorphosis of a Shuttered Butterfly! 