Quote:
|
It's not too bad to set up, and it doesn't even need to be installed on a server.
|
This is what I was wondering about myself. I've used CVS for other (non-FIRST related) projects, and, in general, think it is very useful. However, I feel it would probably be best to run CVS locally at the competition -- we only have one laptop for programming, anyway. I wasn't aware how to do this, so I did some research on cvshome.org and found this (and not much more):
Quote:
There are two ways to run CVS on Windows 95/NT. The first is as a client, talking to a CVS server on a Unix box. This is the recommended setup and is commonly used.
The second way is known as "local" or "non-client/server" CVS. This lets you run CVS if you have only Windows machines. However, due to issues (a) with local CVS on Windows, and (b) with the suitability of Windows as a server operating system in general, we would generally recommend this more to try out CVS and get a feel for it rather than for production use.
|
Source [cvshome.org]
What are the issues of using CVS with windows that are pertinent (windows bashing aside, of course)?
Well, after some more searching, I found a help file for TortoiseCVS that'll let me get a local repository -- it's the one I have installed, after trying WinCVS and not liking it much; are there better ones out there? Also, does anyone know of any possible issues with setting up a server for build season, and then using a local repository at competition?
For an idea of just how helpful this will be ... consider that two years ago my brother had the ingenious idea of naming successive versions of programs so that their values got closer and closer to pi (3.14159...). Well, not that there's anything wrong with that, per se, but he didn't tell anyone, started with a 9, and there was some bit about perfect numbers thrown in. Needless to say, when one of our mentors was looking through the code, he became somewhat confused.