[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Missing CVS Windows Client

From: Rod Macpherson
Subject: Re: Missing CVS Windows Client
Date: Wed, 1 Feb 2006 18:54:06 -0800

I would add that "to only have Windows machines" actually means to have a company policy that precludes the use of even one instance of a more reliable and secure operating system. The cost of such a system would be well below the noise floor for even the most modest budgets. I think you have to have an operation that is fully emersed in Windows and has zero exposure to Linux or OS X or what have you.

On 2/1/06, Spiro Trikaliotis <address@hidden> wrote:

* On Tue, Jan 31, 2006 at 02:16:11PM -0800 Mark D. Baushke wrote:

> Given that CVS provides only a windows client, not a windows server,
> the CVSNT fills an important niche in that it is capable of acting as
> either a client or a server.

This is not true. cvs.exe (the "cvshome" version) can be used as a
server on Windows, you just need anything that wraps it in an NT
service. (I hope we do not speak of a Win 9x/Me installation as a
server; anyway if we would do, it would be even easier to run it
permanently, as no service is needed.) Cygwin allows for this
("cygrunsrv"); in fact, if you install cvs.exe as a cygwin packet, you
are asked if you want to use it as a server. There are other solutions
like "anysrv.exe" (from Microsoft) which should be able to use it the
same way.

Thus, there is no reason to use CVSNT just because you want to have your
repository on Windows. There might be other, technical reasons, but this
is another question.


Spiro R. Trikaliotis                                

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]