While I have pretty much all my code in source control of some kind (originally subversion, now mainly mercurial), the only repos that’s externally accessible is YAK for WordPress (currently a subversion repos hosted at Sourceforge). For something like my quick (read hack-job) attempt at the Stomp protocol, that’s somewhat less than optimal, since I do occasionally (i.e. like today) get updates — so either I have to upload multiple versions, or just overwrite the current version. Which isn’t much use if someone wants to track back to previous revisions.
So, after coming across Bill de HÓra’s “Mercurial First Impressions” and subsequent “Setting up Mercurial on TextDrive” a few weeks ago, it seemed a good time to do something about the situation.
Installation went reasonably well, apart from the obligatory, and rather obscure, Apache error: “Premature end of script headers” — where it took me an embarrassingly long amount of time to figure out that the hg directory needed to be chmodded to 755 as well as the hgwebdir.cgi file (despite the fact I’d checked the file and directory permissions a couple of times during the process… sigh).
The URL for the stomp.py Mercurial repository is now:
http://www.briggs.net.nz/hg/stomp.py/
To checkout the latest copy you can use the following command:
hg clone http://www.briggs.net.nz/hg/stomp.py stomppy
After which hg update will keep you in sync with the (all too infrequent) changes.
Now have to decide whether I want to move YAK off sourceforge and into its own Mercurial repository. The control-freak, tech-geek part of me, gleefully says yes. The lazy, I’ve-got-too-much-other-stuff-to-do part says “pass”.
Time will tell… hopefully before I start arguing with myself.
i’ve been looking to switch to something - probably Hg.
currently using darcs — there’s an annoying exponential slowness problem in darcs
I don’t know much about darcs, but one thing I don’t necessarily like about Mercurial, is the lack of local branches. That was one exceptionally cool feature of Git that I miss since deciding to try Hg. Hopefully it might be added in later releases.
In relation to your slowness problem, I can report that I’ve replayed about 10000 subversion transactions into an Hg repository, and while it’s not as snappy as it was, it’s certainly not groaning.
For example, after an svn update (taking about 1m 21s), the first hg status took 23s, the second 11s. The commit took about 3s, and after that hg status now takes around a second.
Not sure how that might compare…?