Re: CVS and Binaries

[Nils9]

Ok its clear, that CVS is not for merging binaries.. But can I, theoretically,
make my own wrapper which converts the binary into some sort of 
mergeable text (uuencode for example) which encodes binary before
it gets into repository, and reverts ir back when file is checked out?
I know it will take up more space, but less than keeping exact copy
of each binary version. Sometimes we need  to keep binaries in CVS.
I'm not into details how the CVS internals work, but I'd like to.

-Nils Jakobson
SWHTechnology

----- Original Message ----- 
From: "Greg A. Woods" <address@hidden>

> > I want to do revision control on files such as Visio diagrams and
> > Access applications.  These files are "binary" format.  I am currently
> > a user of CVS for my text based source, and I am quite happy with it.
> > I have looked at Visual Source Safe, and it seems like a good tool for
> > storing files of this kind.  However, I don't like the fact that I
> > have to have two sepaprate repositories: one for text base source and
> > one for binaries.  Our CVS repository is also running under Linux,
> > where VSS will not run.  I'd like to keep my repositories on the same
> > physical box.
> 
> Well, like it or lump it, but you've got two very different classes of
> files that require two very different, indeed antithetical, processes
> for handling their change management.  It does not make sense to try to
> lump two such different things into one tool.
> 
> Use the right tool(s) for the job(s).
>