Using Mercurial with your centralized version control June 29, 2007
Unsurprisingly, I’m not the only one using a distributed version control system in conjunction with / to improve upon my centralized version control system at work, and with the various open source projects I touch that use CVS or SVN. The Rock Star Programmer (not sure of his name/nic) gives a quick look at Using Mercurial to Work Around Centralized SCM Limitations. It’s similar to what I was saying in Why you should be using a distributed source control system. You may want to grab a copy of my flow chart for using Darcs with SVN/CVS if you want to try his idea for Mercurial. It’s conceptually the same.
Regarding Mercurial, I’ve given it a quick try and while it is boatloads faster than Darcs it requires configuring a CGI script on a server somewhere if you want to share your repository with others. It does have a built in server but that’s really only useful to people who only want to share over a lan. Darcs doesn’t require this. Just upload your current darcs repo to any standard web server, or put the files anywhere they can be accessed by others, and you’re done. The Darcs client is smart enough to check out from the statically served files on a server or wherever you happen to have placed the repo on your filesystem. I’ll probably stick with Darcs for now because it just makes my life easier to not have to configure a cgi every time I want to share a new repo with people. Especially since I still haven’t figured out why it’s not working for me.
[Update] Related posts:
Using Darcs WITH Subversion / CVS
Using Darcs with SVN / CVS Flow Chart
Why you should be using a distributed source control system
Popularity: 3% [?]
Leave a Reply