Re: Running standard CVS and CVSNT on the same repository?
Somewhat belated answer here: I wrote: I run a CVS server on FreeBSD, currently cvs v1.11.5 because that's what came with my FreeBSD installation. I access this server from the same FreeBSD box, from another FreeBSD box, and from an assortment of Windows machines, currently all using standard CVS under Windows. I'm wondering if I can install CVSNT on the server FreeBSD box and start letting Windows machines use that as their server instead of the standard CVS on that box, without causing problems such as repository corruption, incompatible repository changes made by one server and unreadable by the other, etc. I assume I'd be fine suddenly making everyone use the CVSNT server, but then I'd be worried about updates to FreeBSD itself, which might make use of the stock CVS. On Mon, Jun 07, 2004 at 10:50:43AM -0400, Carucci, Jason wrote: Why not just keep the CVS installation the same on your server and install CVSNT on your Windows machines? This is the setup that I'm using and it works just fine. I understand that a CVSNT server supports features that the stock CVS server does not support, and that CVSNT clients use those features to great advantage. I therefore figured I'd need a CVSNT server to make it worthwhile to use CVSNT clients. Wrong? -- Doug Lee [EMAIL PROTECTED]http://www.dlee.org Bartimaeus Group [EMAIL PROTECTED] http://www.bartsite.com Is your cucumber bitter? Throw it away. Are there briars in your path? Turn aside. That is enough. Do not go on to say, `Why were things of this sort ever brought into the world?' --Marcus Aurelius ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Running standard CVS and CVSNT on the same repository?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Lee [EMAIL PROTECTED] writes: Somewhat belated answer here: I wrote: I run a CVS server on FreeBSD, currently cvs v1.11.5 because that's what came with my FreeBSD installation. I access this server from the same FreeBSD box, from another FreeBSD box, and from an assortment of Windows machines, currently all using standard CVS under Windows. I'm wondering if I can install CVSNT on the server FreeBSD box and start letting Windows machines use that as their server instead of the standard CVS on that box, without causing problems such as repository corruption, incompatible repository changes made by one server and unreadable by the other, etc. I assume I'd be fine suddenly making everyone use the CVSNT server, but then I'd be worried about updates to FreeBSD itself, which might make use of the stock CVS. On Mon, Jun 07, 2004 at 10:50:43AM -0400, Carucci, Jason wrote: Why not just keep the CVS installation the same on your server and install CVSNT on your Windows machines? This is the setup that I'm using and it works just fine. I understand that a CVSNT server supports features that the stock CVS server does not support, and that CVSNT clients use those features to great advantage. I therefore figured I'd need a CVSNT server to make it worthwhile to use CVSNT clients. Wrong? There are indeed a few features that are in the CVSNT server that are not yet in the CVS 'stable' 1.11.x version and one or two that are as yet missing from the 'feature' 1.12.x version. (see http://www.cvsnt.org/wiki/CvsntAdvantages) -- MergePoint processing (http://www.cvsnt.org/wiki/MergePoint) You could use the cvshome version with more tags to do the same thing, but for at least some kinds of uses, this is reportedly a nice feature (I have not used it myself). -- :sspi: authentication (Windows domain accounts /passwords). This may not get you much with a CVSNT server running on FreeBSD. -- SSL encrypted :sserver: authentication (use :ext: with CVS_RSH=ssh for similar levels of security) -- Branch ACLs with 'cvs chacl' and 'cvs lsacl' instead of being configured via add-on scripting. -- LockServer on a second port replaces filesystem-based locks provides file level locking... Using a LockDir approach with CVS on a memory filesystem is similar. -- More triggers (eg, postcommit) -- Supports Unicode files with additional keyword expansion switches (I'm not sure if you will need this). -- Atomic Checkout behavior (I have not looked closely at this feature.) -- Efficient storage of binary files using binary deltas. (CVS discourages use of binary files right now.) -- Extended modules functionality using modules2 file (I have not looked closely at this feature). Which features did you need that are not in the CVS version yet? -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAy9yC3x41pRYZE/gRAnozAKCx28i2XR8Eh3gS3BXWNKnylSaywgCeLawy wmck3vbZXcr6RnKrOBuf/Qo= =fh8G -END PGP SIGNATURE- ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: Running standard CVS and CVSNT on the same repository?
Mark D. Baushke wrote: [very nice summary of CVSNT features beyond cvshome (thanks much Mark!) deleted; see below for full messages] Which features did you need that are not in the CVS version yet? I just know some clients, notably the CVSNT client of course, say I'd get better results with the CVSNT server. I think the cvs ls command may have been one I'd need, but I also think that's being added to the cvshome version now. The rest of this message is the full context with no further comments from me. On Sat, Jun 12, 2004 at 09:48:02PM -0700, Mark D. Baushke wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doug Lee [EMAIL PROTECTED] writes: Somewhat belated answer here: I wrote: I run a CVS server on FreeBSD, currently cvs v1.11.5 because that's what came with my FreeBSD installation. I access this server from the same FreeBSD box, from another FreeBSD box, and from an assortment of Windows machines, currently all using standard CVS under Windows. I'm wondering if I can install CVSNT on the server FreeBSD box and start letting Windows machines use that as their server instead of the standard CVS on that box, without causing problems such as repository corruption, incompatible repository changes made by one server and unreadable by the other, etc. I assume I'd be fine suddenly making everyone use the CVSNT server, but then I'd be worried about updates to FreeBSD itself, which might make use of the stock CVS. On Mon, Jun 07, 2004 at 10:50:43AM -0400, Carucci, Jason wrote: Why not just keep the CVS installation the same on your server and install CVSNT on your Windows machines? This is the setup that I'm using and it works just fine. I understand that a CVSNT server supports features that the stock CVS server does not support, and that CVSNT clients use those features to great advantage. I therefore figured I'd need a CVSNT server to make it worthwhile to use CVSNT clients. Wrong? There are indeed a few features that are in the CVSNT server that are not yet in the CVS 'stable' 1.11.x version and one or two that are as yet missing from the 'feature' 1.12.x version. (see http://www.cvsnt.org/wiki/CvsntAdvantages) -- MergePoint processing (http://www.cvsnt.org/wiki/MergePoint) You could use the cvshome version with more tags to do the same thing, but for at least some kinds of uses, this is reportedly a nice feature (I have not used it myself). -- :sspi: authentication (Windows domain accounts /passwords). This may not get you much with a CVSNT server running on FreeBSD. -- SSL encrypted :sserver: authentication (use :ext: with CVS_RSH=ssh for similar levels of security) -- Branch ACLs with 'cvs chacl' and 'cvs lsacl' instead of being configured via add-on scripting. -- LockServer on a second port replaces filesystem-based locks provides file level locking... Using a LockDir approach with CVS on a memory filesystem is similar. -- More triggers (eg, postcommit) -- Supports Unicode files with additional keyword expansion switches (I'm not sure if you will need this). -- Atomic Checkout behavior (I have not looked closely at this feature.) -- Efficient storage of binary files using binary deltas. (CVS discourages use of binary files right now.) -- Extended modules functionality using modules2 file (I have not looked closely at this feature). Which features did you need that are not in the CVS version yet? -- Mark -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAy9yC3x41pRYZE/gRAnozAKCx28i2XR8Eh3gS3BXWNKnylSaywgCeLawy wmck3vbZXcr6RnKrOBuf/Qo= =fh8G -END PGP SIGNATURE- -- Doug Lee [EMAIL PROTECTED]http://www.dlee.org Bartimaeus Group [EMAIL PROTECTED] http://www.bartsite.com The U. S. Constitution doesn't guarantee happiness, only the pursuit of it. You have to catch up with it yourself. --Benjamin Franklin ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: Running standard CVS and CVSNT on the same repository?
Why not just keep the CVS installation the same on your server and install CVSNT on your Windows machines? This is the setup that I'm using and it works just fine. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doug Lee Sent: Saturday, June 05, 2004 4:33 PM To: [EMAIL PROTECTED] Subject: Running standard CVS and CVSNT on the same repository? I run a CVS server on FreeBSD, currently cvs v1.11.5 because that's what came with my FreeBSD installation. I access this server from the same FreeBSD box, from another FreeBSD box, and from an assortment of Windows machines, currently all using standard CVS under Windows. I'm wondering if I can install CVSNT on the server FreeBSD box and start letting Windows machines use that as their server instead of the standard CVS on that box, without causing problems such as repository corruption, incompatible repository changes made by one server and unreadable by the other, etc. I assume I'd be fine suddenly making everyone use the CVSNT server, but then I'd be worried about updates to FreeBSD itself, which might make use of the stock CVS. Comments welcome. -- Doug Lee [EMAIL PROTECTED]http://www.dlee.org Bartimaeus Group [EMAIL PROTECTED] http://www.bartsite.com Characters live to be noticed. People with character notice how they live. -- Nancy Moser ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Running standard CVS and CVSNT on the same repository?
I run a CVS server on FreeBSD, currently cvs v1.11.5 because that's what came with my FreeBSD installation. I access this server from the same FreeBSD box, from another FreeBSD box, and from an assortment of Windows machines, currently all using standard CVS under Windows. I'm wondering if I can install CVSNT on the server FreeBSD box and start letting Windows machines use that as their server instead of the standard CVS on that box, without causing problems such as repository corruption, incompatible repository changes made by one server and unreadable by the other, etc. I assume I'd be fine suddenly making everyone use the CVSNT server, but then I'd be worried about updates to FreeBSD itself, which might make use of the stock CVS. Comments welcome. -- Doug Lee [EMAIL PROTECTED]http://www.dlee.org Bartimaeus Group [EMAIL PROTECTED] http://www.bartsite.com Characters live to be noticed. People with character notice how they live. -- Nancy Moser ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
