Having installed mercurial via macports, any hg command fails with:
<nasty Traceback snipped>
ValueError: unknown locale: UTF-8
This is mercurial 0.9.5 and Python 2.5.1, but its seem that its caused by Leopard’s Term.app not setting the local encoding correctly. To resolve this, add the following to .profile:
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
as noted in the mercurial mailing list.
When installing SVK (2.0.2) via MacPorts (port install svk) make sure that CPAN is installed and has been configured, otherwise the SVK install will go into an infinite loop wating for user input.
This is evident with a port install -v svk. Without the -v it will simply appear to hang at the Configuring svk step); see also MacPorts bug #12050. The problem is that because CPAN has not yet been configured, it is prompting for the configuration that it needs in order to install SVK.
The first time cpan is run from the command line, it will prompt for configuration data; the process can be re-run using o conf init from within the cpan shell, and individual variables can be set with o conf <variable> <value>, e.g.:
cpan> o conf wget /opt/local/bin/wget
to set, and to unset:
cpan> o conf wget ""
I also ran into this rather less-than-obvious error message compiling Objective-C code on MacOS X 10.5:
syntax error before ‘AT_NAME’ token
I eventually resolved it thanks to this blog entry. The compiler was moaning about a missing @end in a header file.
SVK is a great source control and versioning solution. I particularly like the idea of having local access to an entire respository while still having the safety of an off-site upstream server.
As its written entirely in PERL, SVK is fairly portable (but there’s a "but" coming), but (ah, yes … there it is) while it works flawlessly on my Gentoo system, I’ve had problems getting it to work on Windows. Win32 binaries are available, but they rely on plink for svn+ssh, and I’ve not been able to get the combination to work. I elected instead to run the standard CPAN distribution of SVK under Cygwin. This, of course, brought its own set of problems.
I’ve posted a wiki article that outlines the steps that I followed to get SVK running under Cygwin.
I’ve discovered that it is possible to configure svnserve such that multiple users can commit under their own (svn) names while sharing a single system account (via svn+ssh). It might be handy for those who have subversion respository in a shared hosting environment.
The details are available here.