Slashdot Mirror

I guess you didn't search very well, or else you would have found cvsnt, which was "a better cvs than cvs" way before svn ever existed.
Here:
http://cvsnt.org/wiki or http://www.march-hare.com/cvspro/

Unfortunately you didn't say which platform you use so I assum it's Windows else on Linux you certainly would use CVS. On Windows you could use CVSNT (http://www.cvsnt.org/wiki/).

O. Wyss

There are lots of such tools, including CVS, Subversion (SVN), GNU arch, Monotone, Aegis, CVSNT, Darcs, FastCST, OpenCM, Vesta, Superversion, Codeville, Bazaar, Arx, and Bazaar-NG.

"The better SCM initiative was established to encourage improved OSS/FS SCM systems, by discussing and comparing them. Among other things, see their comparison file. Zooko has written a short review of OSS/FS SCM tools. Shlomi Fish's OnLamp.com article compares various CM systems as does his Evolution of a Revision Control User. The arch folks have developed a comparison of arch with Subversion and CVS (obviously, they like arch). Another pro-arch discussion is Why the Future is Distributed. A pro-subversion discussion is available at Dispelling Subversion FUD. Slashdot had a discussion when Subversion 1.0 was announced. Kernel traffic posted a summary of a technical discussion about BitKeeper. Brad Appleton has collected lots of interesting SCM links. jemfinch has some interesting essays about SCMs (he uses the term VCS), including why he thinks the approach to branches used by Darcs, Arch, and Bazaar-ng is a poor one. A brief overview of SCM systems that can run on Linux is available."

There are lots of OSS/FS software configuration management (SCM) tools. CVS, Subversion (SVN), and GNU arch get lots of press, but there are many others such as Aegis, CVSNT, Darcs, FastCST, OpenCM, Vesta, Codeville, Bazaar and Bazaar-NG.

You might also take a peek at my paper Software Configuration Management (SCM) Security.

CVSNT is an actively developed, native port of CVS to Windows, but which also runs on Linux, that implements at least the first and third points here. I'm not sure what you mean by the second.

john

CVSNT http://cvsnt.org/wiki is actively maintained and has many improvements compared to standard CVS. It is definitely worth having a look at if standard CVS does not give you what you want.

And before you start complaining: it runs on Linux as well as Windows (don't know about other *nix'es).

Unfortunately it has got a bizarre release cycle which makes it hard to figure out which versions are stable, but if you use a conservative approach and monitor the development mailinglists it can be acceptable. I have been using it successfully in a production environment for over a year without any serious problems. And we were very happy with the extended functionality, especially the improvements regarding merging between branches.

...and I'm not just talking SVN (which is quite successful at its "better CVS" goal, though I prefer Arch with its "better revision system" intent): CVSNT

Why it's so rarely used (with the exception of being packaged with the major CVS client GUIs on Windows), and why so few Linux distributions package it, has always been a mystery to me.

as much as I use Subversion and other modern alternatives CVS is not dead.
just take a look at what the previously win32-only CVSNT client/server package can do for you.
it runs perfectly fine on GNU/Linux and also has commercial support if needed.

You can download CVSNT from this web site.

CVS (Concurrent Versioning System) is definitely the way to go.

Here are some links to get you started:

CVS On Windows

WinCVS GUI (very nice, uses Python undeneath)

Tortoise CVS

CVS NT Wiki

Component CVS for Windows

All of these are CVS for Windows tools. CVS is a great revision control system.

the windows version of cvs server.

On the other hand, cvs isn't terrible - and you don't need to be doing OSS or huge # of devs to warrant its use. Cygwin allows you you run in windows, and there is also a windows version of the cvs server.

But look, if you are developing something windows based, and using MS products or IDE's, VSS is not out of the question...it plays well with other MS tools, so it might make the most sense.

Due to the fact that SVN isn't available for Windows (a native port, no cygwyn stuff), I recommend either Perforce or CVSNT + WinCVS. I've used CVSNT at work and home for some time and it works great.

CVS on Windows has come a long way. For the CLI and server side check out CVSNT. The CVSNT guys have done work on smoothing out merges, and are looking into changing out RCS with a real DB - giving the possibility of scaling, meta-data handling and renaming. CVSNT has also been ported back into Linux.

For a kick-ass Windows client check out Tortoise CVS - it integrates into the explorer shell, shows you icon overlays for CVS status and allows right-click access to almost all CVS commands. Everyone in our office - even non-technical folk who freak at a CLI - use Tortoise to access CVS.

I was checking in source code in VSS, and it was like "bleep, bleep, bleep, bleep, bleep!" And then, like, half of my repository was gone. It was a really good repository. I had to code it again twice as fast so it wasn't as good. It's kind of.... a bummer.

Anyway, our VSS never crashed after using it for about 5 years, but ever since I was hired three years ago, I advocated for CVS. I learned a lot in how to initiate change processes, and after about a year, I put together a document comparing the feature sets of VSS to CVS. JBuilder integration with CVS was a nice feature, since that's what we use, It was CVS's excellent branch management capabilities that ultimately drove us away from VSS, since we were starting to need to do branching on stable releases during the next version's development cycles. VSS sort-of does branching, but very poorly. I had to document WinCVS 1.2 myself for the development team, but since the switch, our revision control management has been substantially more useful, and now we have a sense that it's working for us rather than working for it like with VSS.

We didn't need any BSD or Linux boxes. We use CVSNT at http://www.cvsnt.org and it works like a charm :-). It runs as an NT service, and we're currently running it in pserver mode. It supports NT authentication, but my development team is spread across several domains since it's a multi-organization development effort. In your case, NT authentication probably works, or if you're using ActiveDirectory, it supports kerberos and other stuff, too :-).

We're going to set up the ViewCVS web interface soon so that we can get server-side views of our repository. The TortoiseCVS (sp?) Explorer integration is very nice, too, so you can see what files are modified and such right in the Explorer.

For us, CVSNT, WinCVS 1.2, and TortoiseCVS works very well :-), and it's all on Windows.

That looks like a nice, standard mis-informed Slashdot post to me.

For Windows, there is CVS NT which works great. Then you can use Igloo for IDE integration. Or the even cooler Tortoise CVS for explorer integration (an easier to use source control tool I have yet to find).

OR, there is always Subversion if you don't want CVS. Subversion also has a Tortoise port.

Or, back in the closed source world, Perforce and I'm sure a handful of others.

So look at cvsnt. It meets your requirements:

• Runs a cvs server as a simple native win32 service under WinNt, Win2K.
• Has a Win32 style control panel to configure the service.
• Builds with Visual C++, so no funky cygwin cruft required.
• Allows pluggable network protocols as separate dll's, so you can add or remove a protocol without needing to restart the service.
• Offers additional features beyond core CVS:
  • 'ls' command to list the contents of the repository, not just dump modules file as 'cvs co -c' does.
  • sspi and ntserver wire protocols for native Win32 authentication, encrypted network traffic.
  • User impersonation (equivalent of Unix setuid).
• Good support from active mailing list.

There is quite a mature native Windows port of cvs that we've been using for quite some time.

john

Ok,

1. Install Cygwin. Yeah it's a dumb shitty-ass pathetic installer, and those who built it should be slain and their bodies fed to pigs, but hey, the tools are nice when you are done.

2. Install CVSNT. Easy install, take it all.

3. Do yourself a favor. Add those two to the path. Right click on My Computer, select Properties, click the Advanced Tab, and click on Envionment Variables. Under System Variables, find the PATH statement, and add in the following :
;c:\cygwin\bin;c:\Program Files\CVS for NT

4. While you are in there, add a new System Variable: CVS_RSH and set it to SSH.

Now, it's all set up and ready to use, as long as you know how to use CVS. (an entirely different question).

Now, if you like GUI tools at all I highly recommend the following :

TortoiseCVS -- This can EASILY be setup to use SSH. As a matter of fact, the builds past 0.49 have it all ready to go. Read the docs, and you'll see.

and WinCVS -- Which is the king daddy of CVS Gui Apps for Windows. A bit clunky for my needs.

and Jalindi Igloo -- A SCC API plugin for CVS. What's that? -- It's allows Windows Development tools to use CVS instead of Visual Source Safe (VSS=a plague!). Sweet, simple and kinda nice if you like that kinda thing.

--
Wuff