Re: Support for Windows 10 (CVSNT vs. SVN and CVS 1.x)

Hi Michael,

It sounds like you don't know much about CVSNT, so let me correct a
couple of misconceptions.

> If you're willing to pay, March Hare will sell you a client, but again
> that's a command line tool.

No - CVSNT (what we now call CVS Suite) is a single installed combining
TortoiseCVS, WinCVS, WinMerge, Release Manager, Workspace Manager,
Control Panel, CVSAgent and CVSNT combined.

The March Hare solution has always been a 'combined' installer with all
the components tested together into a single supported package.

We supplied the TortoiseCVS and WinCVS projects with a simple 'command
line only' installer for bundling in their community projects.

You've always been able to run CVS 1.x on Windows (or cygwin) - but
CVSNT was created to address all the problems that doing that created
(where you ended up with HELLO.cpp, Hello.cpp and hello.cpp in your
repository).  Plus of course CVSNT added a LOT of extra features aimed
at commercial software developers.

> If you want to do some work yourself, you could try fixing TortiseCVS
> (http://www.tortoisecvs.org/development.shtml) yourself. I don't know
> where the Win10 problems lie, so I don't know if you'd need a new
> CVSNT version or not. If you do, I suspect you could port the current
> CVS client (http://www.nongnu.org/cvs/) without too much trouble, if
> March Hare can't help with a new release of CVSNT.

Because it took about 7 man years to create CVSNT 2.5 from the CVS 1.11
sources, someone else can do it 'without too much trouble'?  

> Basically: No one is doing free development on CVS 

Both CVS and CVSNT are under active development.  The CVS 1.x
development may look stalled if you look at savannah for reasons it is
not politik of me to go into - but I know quite a lot of work and
discussion is going on behind the scenes.  There is a separate private
mailing list for that.

There are new releases of CVSNT every few weeks which we announce via
twitter feed.


> That's really down to the fact that it frankly
> doesn't do everything that you want in a source control system (it
> doesn't track history across file renames. 

CVSNT has tracked the history across file renames since somewhere in
2005 from memory.  Ditto 'automatic commit identifiers' aka 'atomic
commit'.

Many of the features of CVSNT are still fairly unique, eg: failsafe
audit to sql database, user defined commit labels.  Full lists here:
http://march-hare.com/cvsnt/newfeatures/


Regards,


Arthur Barrett
Product Manager

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot