Regarding helper apps for SVN I use ZigVersion:
If you have no need to upgrade svn from the version that comes with
Leopard then ZigVersion is a great product.
Academic licenses are free. In my experience, ZigVersion is quite
stable, very easy to use, and has an intuitive (Mac-style) interface.
I use it to maintain my working copies of my solo and collaborative
projects, be they programming (mostly fortran of all flavors and eras
from 77 forward), writing (tex), and/or scholarship (bibdesk)
intensive, on both of my machines.
Sadly, roughly a year ago the developers stopped answering questions
on their forums (one post this calendar year and that was simply
posting something I lacked the privileges to post and sent to them via
email with a request for its posting). This silence, along with the
fact that there has been no new code released in at least six months
at ZigZig software suggest that ZigVersion is no longer being actively
developed. So, if you do want the merging capabilities found in
subversion 1.5 you will probably find ZigVersion will not meet your
needs (I run it against 1.4.x). On the other hand, if you are just
looking for a stable, clean, Mac interface that works beautifully with
repositories of all shapes and sizes running under subversion 1.4.x,
ZigVersion is well worth a look.
Please note though, that if you use subversion you are bound to have
some serious problems with files created by several very useful Mac
OmniGraffle (can work around this in OG by saving flat files)
Others that create packages instead of flat files
Subversion 1.4.x chokes on packages when you change anything in a
working copy and then try to check it in again. These folders
masquerade as files and subversion does not (at least as of 1.4.6)
deal well with this. I suspect this is not really subversion's fault,
as I think what happens is that the application erases old files
within its structure and creates new ones, thereby creating chaos for
the version control software's tags in the working copy. The folks at
ZigVersion provided a Perl script to get around this problem that
involves a lot of moving files around, deleting the old package,
creating a new one, passing through a tar file state, etc. If anyone
is interested the URL for the forum entry with the direct link to the
download for that script and instructions for its use is...
I have used this script successfully for quite a while. It has made
using subversion with those Mac apps that rely on packages instead of
flat files possible.
On Jul 9, 2008, at 10:42 AM, Derick Fay wrote:
>> A scenario likely to occur would be that I will keep the master.bib
>> in an SVN repository, travel to some library without wi-fi internet
>> access with my PowerBook, discover some new books that I add to my
>> working copy of master.bib, make some changes to particular pubs that
>> already feature linked and autofiled files, save and commit my
>> when I have internet access again. Would be great if all the links
>> intact afterwards.
> This is a bit off-topic but I have been thinking about using
> subversion to manage versioning etc. on several writing projects.
> Everything I've seen seems to be oriented towards team / multi-user
> scenarios but it also seems that people use it for single-authored
> projects. Stephan (and others!) , do you have any recommendations on
> SVN workflow, helper apps, shortcomings etc? Prefs. for SVN vs.
> Mercurial or other alternatives?
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> Bibdesk-users mailing list