RE: How well does CVS handle other types of data?

[Cameron, Steve]

Just thought I'd mention one problem with trying to store binary
files in CVS that nobody has mentioned yet....

It's not too hard to get diff to run out of memory with binary
files, (compared to ascii files.)  I have one file in my repository
that I can't commit to because of this.  Luckily, it's obsolete, and
the commit that I would like to do is a "cvs remove".  But I can't,
so it gets checked out all the time and ignored.  Tolerable, but 
not ideal.  (The file _is_ rather huge to begin with, so maybe it doesn't
actually come up that much.)

On the issue of whether storing binary files in CVS is a good
idea, vs. trying to use "something else" in conjuction with CVS,
my experience has been that putting the binary files in CVS works
well enough, (apart from the above problem.)  The advantage,
(having one tag that you can do a "cvs checkout" and get _everything_
you need.)  outweighs the disadvantage, (that files are not mergeable)
for us anyway.  Probably this has something to do with the nature
of our binaries, (always thrid party deliverables that we just check in, 
merging boils down to  trivial selection.)  That's how it's worked out
for us anyway.  YMMV.

Back to lurk mode.  

-- steve