Meng Lin's Byte-Wise Words

After searching through the web, I managed to find bits and pieces about upgrading subversion from 1.6 to 1.7 on CentOS. Unfortunately , it is like unraveling a puzzle, every blog starts from a slightly different corner and came across different blocks. I was strapped in perpetual trying and failing because of this. So I thought I better summarise and share my whole experience, along with the pitfalls while trying to work it out. The upgrade, in a nutshell, is a process of uninstalling the current version of svn, and download, compile and install the target version. Prerequisites CentOS, SVN 1.6 Recipes and Tasting 1. Remove current svn That's right! You heard me, be brave and remove svn using: # yum remove subversion 2. Download target version of svn Go to the following location: # cd /usr/local/src/ And download the the target version of svn using: # wget  http://apache.mirrors.timporter.net/subversion /subversion-1.7.16....

Despite the real world benefit like being able to review and rollback,  I believe being able to grow and evolve with your code is one the reasons why   version control is such an essential part in software development. What have we got across the board? In the beginning, there is Subversion. I've been using a couple of SVN tools to  manage my code at work or for fun for years, which are   T ortoiseSVN , SmartSVN  and  VirtualSVN . (ref:  How to Set Up a Source Control ) Subversion tools use tree structure to represent the trunk and branches of your code, which is easy to understand and use when committing, branching, tagging and etc. But there are problems with svn tools too.  In svn, it is exceptionally expensive to branch and merge. Branching always loads with a complete copy of the code base on server, and being able to branch locally does not exist. And  you would never feel bored when  m erging more than a dozen file...

In an multi-developer environment, version control turns out to be a very important thing to do before crack on coding. There are certain options while setting up svn repository: 1. use public hosting service, e.g. google code, 2. set up locally repository, 3. set up network share. By comparing the usability and impact of the solutions, the last way of accessing repository seems to be more of a feasible action. Even though dealing with day-to-day check in check out is an easy task using  TortoiseSVN , to set up a network share svn repository requires a little bit more than that. That's why  VisualSVN Server came to the rescue. The step-by-step guide of setting up network share repository is as follow: Server-side 1. Download and install VisualSVN Server 2. Open Visual SVN Server, right click on 'Repository', select 'Create New Repository' 3. Type in a name for the repository, also tick the check box 'Create default structure', which will give a ni...