RE: cvs update; merge

[Andreas Lindgren]

Larry Jones writes:
> > moral:   If you are using any binary files across 
> platforms, default should
> > be binary, not ascii.
> 
> Real moral: Don't use CVS for binary files.

We are moving from VSS to CVS (at last) and have a "culture", or working
process, among the developers how the source handling works. One of the
things in that process is that we have one build machine for each
platform which does daily builds. The resulting build targets and
installation kits are checked into the version handling system for later
tracing, e.g. to have the source code label automatically match a
specific build.

Are there any negative effects (except for the repository growing in
size) of keeping this kind of binaries within CVS? We do not have need
for merging (neither of version branches nor simultaneous edits), or
using any cross-platform features except maybe for .pdf files which are
generated on one platform, but included in the distributions on all
platforms. In other words, the versioning system are for the binaries
only a storage for history.

I have now gotten acceptance and resources to switch from VSS - I would
hate to have to take a step back here...

        /Andreas


Bonus question: Does anyone know if VSS uses some delta storage of
binaries (e.g. 10 consecutive setup.exe) - which makes a VSS storage
more space-efficient?