LyX ⇒ Version Control and Dropbox

[acacio]

Hi Folks,

I am new to version control, but I'm trying to collaborate with a colleague and we thought this would be a good solution: run LyX from a Dropbox and then use version control to make sure that we don't mess it up. Now, version control is supposed to put a lock on the file when someone checks out a document for edits.

However, when I do that, my colleague sees the file unlocked, and can edit it. Furthermore, sometimes (the keyword is sometimes) we get a "ci ..." error, though it is very laconic and doesn't tell us what is going on (just the standard error). I'm running LyX on a Mac, and he is running on Ubuntu, and we're both using version 2.1beta2 (same version). We're both running RCS, but mine is RCS 5.9. Did anybody experience this problem? Any suggestions on how to try to troubleshoot or pinpoint the problem? Could it be a problem of LyX and RCS 5.9, since it's been tested on 5.8 only?

Hopefully my description was clear enough, but let me know if I left something important out.

Cheers,

Acacio

[scottkosty]

It could definitely be a version issue. LyX's RCS I don't think has been tested recently. SVN has recently been improved for a newer version and Git support has been been added, but RCS has been forgotten about I think (which is a shame). A but report would be great:
http://www.lyx.org/trac