Linux CVS Server and Windows CVS Server

[mgorse at mgorse.dhs.org (Mike Gorse)]

There is a fork of the standard CVS to run on Windows called CVSNT 
(http://www.cvsnt.org).  We are using it at work, including a server.  The 
one advantage to it is that it can integrate with the Windows domain for 
its user authentication and file permissions, so it might be useful if you 
already have a Windows domain set up.  What would be best probably depends 
on what you are using in general as a file server.

On Fri, 7 Oct 2005, Greg Rundlett wrote:

> UNLESS things have changed since last time I setup a CVS server, you
> can NOT USE WINDOWS as a CVS server operating system for more than a
> local client, meaning it is only good for a single user.  So much for
> enabling the concept of collaboration.
>
> Actually, I checked the CVS book on it
> (http://cvsbook.red-bean.com/cvsbook.html)
>
> Limitations Of The Windows And Macintosh Versions
>
> The Windows and Macintosh distributions of CVS are generally limited
> in functionality. They can all act as clients, meaning that they can
> contact a repository server to obtain a working copy, commit, update,
> and so on. But they can't serve repositories themselves. If you set it
> up right, the Windows port can use a local-disk repository, but it
> still can't serve projects from that repository to other machines. In
> general, if you want to have a network-accessible CVS repository, you
> must run the CVS server on a Unix box.
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://olduvai.blu.org/mailman/listinfo/discuss
>