Since I’m not a stranger to the Subversion, the first chapter of the book was pretty easy for me to catch up.
Since some of my friends were strangers to the Subversion, we had a short Knowledge Transfer (KT) in which I gave them an introduction to the Subversion.
A few points about it. . .
Earlier the lock – modify – unlock concept was used, which eventually had some drawbacks. The main reason being that, the file gets LOCKED by the user preventing the other user from editing the same file simultaneously. The other users had to wait for the first user to commit his/her work even though there is no need practically.
The subversion uses the COPY – MODIFY – MERGE concept, which needs some manual effort to prevent the conflicts.
Subversion uses the Berkeley DB and the FSFS database for the repository.
Let me tel u the basic commands covered in it too🙂
1. svnadmin create /var/svn/repos
( svnadmin is the function in subversion to perform the admin related works such as creating a repository. Here a new repository is created in the name “repos” )
2. svn add test.c
( svn add is a funcion to add a new file into the subversion repository. Here a new c code is added into the reposiory. NOTE : this command must be run from inside the working copy )
3. svn co file:///var/svn/repos testrepo
( svn co is a function to checkout the latest revision from the subversion repostiory. Here the files are checkedout to a new directory named “testrepo”. NOTE: this command must be run from inside the working copy )
NOTE: a metafile .svn is created automatically when we checkout a repository.
4. svn update
( svn update is a function to update our current working copy comparing it to the subversion repository NOTE : this command must be run from inside the working copy)