A note to myself: The only constant in life, Indy, is change!

I've been using Subversion for version control for a couple of years now. It was quite a change moving from Microsoft Visual Source to Subversion. A different mind set. A different way of doing things.

And then I read about Mercurial today.

Mercurial is one of the new breed of version control systems.

Its major goals include high performance and scalability; serverless, fully distributed collaborative development; robust handling of both plain text and binary files; and advanced branching and merging capabilities, while remaining conceptually simple. It includes an integrated web interface. (Wikipedia)

Basically Mercurial moves away from the paradigm of working with centralized repositories (like CVS and SVN) to support distributed, collaborative development. And at the same time trying to be a simple-to-use system (a big challenge!).

ﾠ

Read more...

Part of rebuilding my laptop was to get Subversion going.

Installed Subversion server 1.4. As I like to access it over http using Apache, I installed latest build of Apache 2.2.

But after making changes to http.conf to get Apache to work with Subversion, Apache server refused to start up. The Apache logs didn't contain anything descriptive on why the server was not starting up.

Then I came across the following warning on the Subversion downloads page:

Note that the Apache modules included in this package was compiled against Apache HTTP Server 2.0, and thus will not work with Apache HTTP Server 2.2.

So that was the problem. Have now uninstalled Apache 2.2 and am installing Apache 2.

Hopefully that will work.