On Jul 9, 2008, at 2:21 PM, Stephan Kurz wrote: > Dear Derick, > > it is not too off-topic (at least for me as BD is an essential, but > only > one piece in my workflow puzzle) as it reflects actual usage > scenarios… > > Derick Fay wrote: > >> 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? > > Since I am relatively new to SVN as well, I am also quite interested > in > other’s feedback. > > My main reasons for using a versioning system at all for my single > authored project: > - backup > - having an overview of what I have done, say, in one month, being > able > to compare and restore versions, etc. > - keeping different versions around is painful, and I always did > something wrong (like, zip your working folder every day and give it a > name with the date or so, and then you copy it to a USB key and lose > this thing)… > - keeping things organized and labelled with proper commit messages > make > my life easier. > - backup again. I have set up a SVN repository on a university > filespace > that is backed up locally and off location three times a day, so my > paranoia of data loss is somewhat easened. > > Main reasons to use SVN: > - I do not need a full blown shared repository thing like Mercurial > for > my needs. > - SVN ships with leopard, so almost everything is already there > - there are GUI tools that looked promising and understandable to me > > My setup: > I use SVNx as a GUI tool to keep my working copies up to date. While > it > may not look too nice and mac-like, it works. > Beware, for accessing repositories via ssh+svn://, you need ssh access > via authorized keys (OS X ships without ssh_askpass, and setting up > passwordless access seemed the most feasible way to work around that). > > Sometimes I also use the SCPlugin Finder plugin. > > I have tried Versions (beta) and another relatively new SVN client > with > a nice timeline view which I cannot remember now, and these both > gave me > an error when I tried connecting to my repository. That kept me with > SVNx though the other clients had a much more mac-like look-and-feel. > >> thanks >> Derick > > Hopefully this helps, > Stephan
I second all of this; I commit to a local repository, then mirror it to Amazon S3 via JungleDisk. Saved my bacon recently when my laptop went illogical (broken logic board), *while doing a time-machine backup*, then the internal drive and the time-machine drive had serious issues; but S3 was cool. The one thing that SVN isn't good for with latex is diffs, the line-by- line orientation is pretty useless for changes of phrases etc. I think there are some word-by-word diff tools out there, but I've never gotten them to work right. Happily Skim notes are a good way to get feedback. --J ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
