I'm a tourist in my own country now. Well, not really -- I'm mostly visiting friends rather than places -- but I still haven't slept in the same place for a week straight. Here are a few photos:
Leif's lovely blue house
Me, Brynn, and Leif on the blue ridge parkway
Dirt Creek Band -- Dad's on banjo
The Amtrak station in Durham
I got a new hard drive for my old laptop and installed Ubuntu on it. The brown is surprisingly nice, and the Applications / Places / System menus seem well-thought out. I went ahead and upgraded to Hoary. No problems here. To me, it's just debian with better gnome support.
I'm trying out bazaar as well. Arch is an interesting phenomenon -- you have a number of smart, strong-minded folks exploring the revision control problem space, with tensions from the different directions (GNU, Tom Lord, Bazaar, PyArch..), but united in their fundamental approach. I find it fascinating that these competing efforts can share a mailing list and an irc channel.
Bazaar does seem to provide some usability improvements over tla. I'm happy with it for now, and since it interoperates with tla-format archives, I imagine I'll use it in the future as well.
I started using hard-linked revision libraries with baz/tla (both greedy and sparse). I ran into some problems at first, because I had emacs set to not make backup files. Because the revision library and the working copy point to the same inode, editing the working copy affects the "pristine" source as well.
The solution to the problem is to turn on backup files, of course. Because I don't like lots of ~ files cluttering up my work space, I set the backups to go to ~/.backups/ with this .emacs snippet:
(custom-set-variables ; just copy the two lines below into the custom-set-variables block '(backup-directory-alist (quote ((".*" . "~/.backups")))) '(make-backup-files t) )
This means that before emacs writes your file, it moves the old copy to ~/.backups. Thus the original inode is not affected, and the revision library keeps its integrity. If you mess up somehow, arch will know anyway -- you just have to remove the revision from your library. The next time you need it, arch will make a fresh copy.