Lifehacker had a reference to a really excellent posting on “Using SubVersion for Writers.”
This is a really good overview, with examples, of how to use SubVersion for writing, web projects, etc.
I personally use and recommend SubVersion, largely because it support explicit “move this file” “this file is now obsolete” and “add these all together” semantics. The Using SubVersion for Writers posting is an excellent reminder of just how helpful and simple SubVersion is, even for small non-technical writing projects.
Installing on MacOS ‘Leopard’ is trivial: it’s already there. To add a GUI, use either SCPlugin to add a SubVersion menu to Finder, or SubVersion Scripts (here’s a great screencast). It is easy to install SubVersion on earlier versions of OSX, as well.
For Windows, I like TortoiseSVN. On Solaris and Linux (Red Hat, Ubuntu), I tend to use the command line.
For reference material, see the “Red Bean book” SubVersion.
Best,
Dak
3 responses so far ↓
Chris // April 30, 2008 at 9:17 pm |
Check out GIT – apparently it’s the next big thing
Benton // June 19, 2008 at 3:10 am |
Somehow i missed the point. Probably lost in translation
Anyway … nice blog to visit.
cheers, Benton.
Dak // June 19, 2008 at 9:01 am |
Thanks, Benton. The idea is that you would use a file repository to save your ‘works in progress’…think of it as an ‘undo’ for entire versions of files. This is something that software developers use all the time, but which writers and other creative professionals haven’t taken advantage of.