[cvsnt] Benefits of CVSNT vs cvs (cyclic) 1.11.x???

Glen Starrett grstarrett at cox.net
Fri May 23 18:52:51 BST 2003


Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.


I believe you should change
   a. ACLs per directory
to
   a. ACLs per directory/branch
but I'm not positive on that since I haven't used that feature yet.

With "c" in that same section, I have read here you could use PAM to hook
into NT authentication from Linux--that would apply to either VS or CVSNT, I
believe, but it is still better than more accounts to manage.

Check the CVSNT wiki for more differences / information.
http://www.cvsnt.org/

Regards,

Glen Starrett


-----Original Message-----
From: cvsnt-bounces at cvsnt.org [mailto:cvsnt-bounces at cvsnt.org]On Behalf
Of Rick Silton
Sent: Friday, May 23, 2003 10:12 AM
To: cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
Subject: [cvsnt] Benefits of CVSNT vs cvs (cyclic) 1.11.x???


Hi,

I'm considering using CVSNT instead of the "standard"
linux distribution of CVS (1.11.3).  The server will
still run on linux, and we will have a mix of *ix command
line, WinCVS, and Tortoise clients (>150 users).  I've done
some testing and generally like what I've found, but need
to have pretty strong justification to support the cost of
upgrading.  So far I've been able to come up with the list
below but I expect I've missed some (or misunderstood some).
Please add, or comment on any of these or point me to some
other information (I couldn't find any useful faq...).

1. Provides better support for current windows clients (yes,
I know that's vague, but I don't believe it makes sense to
run WinCVS 1.3 against a 1.11.3 server...)

2. Pseudo exclusive lock capability that doesn't require
admin command access (suitable for editing binary files
for example) (cvs edit -c)

3. Solves Daylight Savings Time problem (or is it that
WinCVS 1.3 solves it...?)

4. Provides better security capabilities
   a. ACLs per directory
   b. Sserver protocol (I believe is simply pserver over ssl)
   c. Password management

5. Simple repository browse capability (cvs ls)

6. Atomic commit support (but I don't believe this implies
serialization with checkout & update which I believe is
the real issue.  This is also not on by default and I get
the impression it isn't universally endorsed.)

7. Separate locking process (I'm not positive of the benefit.)

8. Actively under development.


Thanks,

- Rick


_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs



More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook