This post originated from an RSS feed registered with Python Buzz
by Phillip Pearson.
Original Post: CVS and Subversion: symlink behaviour
Feed Title: Second p0st
Feed URL: http://www.myelin.co.nz/post/rss.xml
Feed Description: Tech notes and web hackery from the guy that brought you bzero, Python Community Server, the Blogging Ecosystem and the Internet Topic Exchange
Important difference between CVS and Subversion. If you make a symlink in your CVS working dir, say to a directory somewhere else, CVS happily follows the link and assumes that you wanted to move part of your working dir to the new location but still keep it where it was in the repository. This is nice if you have a web project and want to store the web files in /var/www/foo and have a symlink from /home/foo/projects/bar/www that points there.
Subversion, on the other hand, knows about symlinks and lets you add them to the repository so that on checkout, it actually creates new symlinks. This has its benefits, but it means the aforementioned nicety doesn't work any more and you either have to move your whole working directory somewhere public or point Apache at something deep within your home directory...
Previous Topic
