Re: Version Control of Binary Files with Multiple Developers

On Mon, 2004-04-26 at 17:01, Ed Skinner wrote:

>      I'm going to be working on some binary files (OOffice writer, 
> presentation and spread-sheet files) along with some other developers. We're 
> in widely separated locations (AZ, CA and MD) and the files will be on a 
> machine to which we all have a "mount" (via VPN).
>      It's been a while but I don't think CVS will keep us from editing the 
> same file at the same time and, because the files are "binary", the merge 
> tools won't help us.
>      What's the best way to go? (So far we're all on Linux, at least.)
>      Thanks for any suggestions.

Well, I'm going to answer your questions in a few ways:

1) Using CVS you can lock files. This means that everyone else will get
told that they can't have the file now. This can be an effective way to
make sure that only one person is editing the file at a time.

2) The OOo file format isn't actually a binary format. It is a
collection of XML files that are Zipped up. I believe there is a way to
get OOo to use a directory instead of a file, and edit that. In that
way you wouldn't have a binary, and thus merge tools would be happier.
One of the issues that you'll face is that things like images, which
could be added to a document and placed in the ZIP file, won't get
automatically added into CVS. Users would have to be careful to do
this.

3) For group document creation, I've become a big fan of doing things on
a Wiki. While you don't have the complex formatting, it is absolutely
wonderful for getting the text down. I found a link in freshmeat.net
the other day for a docbook based Wiki, which would mean you could have
some formatting too, but I haven't tried it out yet.

4) I'm not recommending anyone do CVS anymore. Subversion is so much
better for so many reasons. Use subversion. (which doesn't directly
solve your issue, but I think it is important to mention)

Hey, when you do decide on a solution, and get some time with it, could
you post a follow up of what works and what doesn't? I personally would
love to know. (hell, you could probably publish the case study in
OSNews or Newsforge or something also)

        --Ted