Kurinchi Blogger Scribbles ... » subversion

Choosing version control system (VCS): Git vs Subversion

kurinchilamp — Mon, 01 Feb 2010 06:49:02 +0000

Git

- Distributed repository system (adaptive work flow models)
- Source control taxonomy: DAG storage
- URI to git directory is where the repository is stored and it always has branches and tags
- Repository root folder contains a .git directory which maintains file history
- Scalability
- Faster, Efficient branching and merging
- License: Copyleft

Subversion (SVN)

- Centralized repository system
- Source control taxonomy: Delta storage
- URI to a subversion depository most commonly adopts /trunks, /branches and /tags directories
- Each folder maintains a .svn directory to store the file history
- Not efficient in scaling
- Not efficient in branching and merging
- License: Copyfree

Subversion SVN: Project organization

kurinchilamp — Fri, 10 Apr 2009 02:42:23 +0000

Subversion Project Organization: Intro

When organizing the repository structure for maintaining the code base, system admins adopt two basic formats for Project organization in subversion. This depends on the needs of the project and it can be varied over a period of time, depending on the scope defined for the code base. Subversion is very flexible in handling these changes and is easier to maintain than most other products in the market.

Subversion: Folder Organization

SVN: First organization is to allow multiple projects which are loosely tied together.

/var/www/svn

/var/www/svn/repos1
/var/www/svn/repos1/conf/
/var/www/svn/repos1/db/
/var/www/svn/repos1/hooks/
/var/www/svn/repos1/locks/
/var/www/svn/repos1/format
/var/www/svn/repos1/branches
/var/www/svn/repos1/trunk
/var/www/svn/repos1/tags

/var/www/svn/repos2
/var/www/svn/repos2/branches
/var/www/svn/repos2/trunk
/var/www/svn/repos2/tags

SVN: Second organization is to have projects organized which are tied to each other. A change or revision in one project is reflected in the other projects as well.

/var/www/svn
/var/www/svn/branches
/var/www/svn/trunk
/var/www/svn/tags
/var/www/svn/project1
/var/www/svn/project2

These two organization form the basis for the other trees that may grow for managing a project or multitude of projects.

Subversion installation steps – Part 1 (Client installation)

kurinchiblogger — Fri, 12 Dec 2008 01:48:01 +0000

Subversion is a version control system software that is used for effective and efficient quality management of projects consisting of any number of files. It is a substantial alternative to CVS repository and has gained popularity in very short time. Subversion is used in many companies ranging from small/medium scale companies to large scale enterprises because of its ease of use compared to other available products in the market.

Below steps describe the installation of subversion client on CentOS / RedHat / Fedora.

Step 1: As we will be modifying certain files inside httpd, we can stop the server.

/sbin/service httpd stop

Step 2: Subversion is available as a yum installation package and it significantly reduces the time for CentOS / RedHat users.
yum install subversion mod_dav_svn

Step 3: Open the file /etc/httpd/conf.d/subversion.conf which will have the following set of lines commented. You can enable the lines which you need.

LoadModule dav_svn_module modules/mod_dav_svn.so
LoadModule authz_svn_module modules/mod_authz_svn.so

DAV svn
SVNParentPath /var/www/svn

AuthType Basic
AuthName “Subversion repos”
AuthUserFile /var/www/svn/htpasswd
Require valid-user

Step 4:
Create the necessary repository directory.

mkdir /var/www/svn
cd /var/www/svn
svnadmin create myrepo
chown -R apache.apache myrepo

Step 5:
Start httpd service in order for the changes to be effective.
/sbin/service httpd start