Is there consensus within this group as to which versions of the
client-server CVS should be downloaded for a Solaris server and NT
client?
Specifically, unless I'm counseled otherwise, I intend to download:
a) WinCVS 1.0.6 (Final/Stable) from //www.wincvs.org/download.html
b) CVS 1.10.5 from //download.cyclic.com/pub
Though I'm tempted by the following newer versions, I don't need the
NT server support, so I won't download them unless you know of some
*other* reason that would make me reconsider:
a) WinCVS 1.1b12 (Beta) from //www.wincvs.org/download.html
b) CVS 1.10.8 from //download/cyclic.com/pub
-------------------
Apart from that choice, I'm also curious about this 'enhanced' version
of CVS from CodeFab that claims to support the cvswrappers file:
a) CodeFab CVS-1_10_3-realwrap for WinNT from //www.codefab.com/cvs.html
b) CodeFab CVS-1_10_3-realwrap for Sun Solaris from
//www.codefab.com/cvs.html
In the standard CVS, the client-server additions weren't made in a way
that would still support cvswrappers; that functionality is reportedly
disabled. Since I do have a small number of resource/binary files to
deal
with in my app, I'm wondering whether this version of CVS would be
preferable.
But perhaps the binary file issue with WinCVS isn't that big a deal,
easily
worked around, and since I've only a few binaries to worry about, maybe
I
should just stick with WinCVS? Plus, I don't see an obvious indication
as
to whether CodeFab's CVS provides a GUI front end.
(Note: The cvswrapper file controls whether a file is marked as binary
according to the file's extension. It also supports revision management
of a directly as if it were a file. So, for instance, a directory of
resource files can be tarred up into a compressed file, which is then
put into the CVS repository. Binary revisions of the tar file are
maintained instead of revisions of the individual files contained within
the directory.)
ANY INFORMED OPINIONS OUT THERE?
