CVS hell

#1 Come on. CVS is use by thousands of open source and professional projects world wide. Other source code control programs are used to manage hundreds of thousands of projects world wide. There is no better way to do this. CVS itself is used by thousands of people in the Torque community. It works.

Please read the documentation about how to move to a new release. I know this stuff works because I am not a programmer and I have walked through the docs step by step to make sure they work. There cannot be anybody in this community less technical than I am.

If you don't know how to use it, why are you attempting to use CVS from the command line? Please, please read the documentation.

#2 Ok that didn't answer my question did it.
If I spend all day every day using CVS I could use it but once every other month is not enough time to stay proficient at it.

#3 Did you look in the directory where you command prompt was when you typed the command? If you did it from Start->Run then look on your desktop or your "my documentents" folder. Failing all that did you try to do a hard drive search for a directory called "torque" Did the CVS give you any output? It should have.

#4 I use windows and winCVS, followed the docs step=by=step and it makes a c:\torque folder when I use it.

I was quite worried and confused about CVS when I first realised it was the only way to stay up to date with Torque, but its an excellent system and works well once you know what its all about :)

If you are having difficulties i think winCVS is much easier than command line (if you're using windows of course)

Good luck
Nick

#5 ...

#6 I got on to the announcement for the torque 1.3 update and everyone was having trouble getting it. One of the comments in there had that command line and everyone said that would work so I did it from within cvs. It seemed to have downloaded the files or said it was updating at least. I assume the engine contains the updated version 1.3 now but the file dates are all from the last time I used cvs like June or so, and the program that it builds doesn't have the new 1.3 particles editor and such in it. Of course now I can't go back to cvs because my daily allotment of use has been exceeded. As for the command line cvs -z3 checkout -r Release_1_3_0 torque does the last word in the command line mean my torque directory or cvs's torque directory.
I understand the need and the use for cvs, I use source safe with visual c but so far cvs has destroyed 2 of my builds by overwriting files, the first one was my fault for not copying the files elsewhere. The second time, cvs found my copy and copied over those files. If the new version was zipped up and placed somewhere I could just grab it and put it where I wanted then I would know for sure. As it stands, I dont know where or what I have. At least I can revert this time. Sorry I'm so stopid..... and thanks for help.

#7

Quote:
torque does the last word in the command line mean my torque directory or cvs's torque directory.

The last item is the "module" or "Directory" you are checking out from the CVS Server.

Quote:
so I did it from within cvs

What does this mean? Are you running win CVS? Either way follow the directions here. If you want to check out the latest without overwritting your working copy, see "Procedure B.3. Checkout" Step #3 and change c:\ to some new directory such as "c:\newDirectoryFor1_3_0"

Hope that helps.

Edited to fix bad link

#8 Here just takes me here....
Yes wincvs is what I have there is another?
I looked all through the directory for doc files and all I see are help files this is all I could find
Checkout module...

Use this option to checkout from scratch a new module on your disk. You need to give the complete path of the module on the server : for example : "myprog/mysubfolder1/mysubfolder2"

#9 Howard, use the GUI - not the command prompt.

If you even did read the documentation, then you wouldn't had made the approach using the console. Try to actually read the documentation, and if it still ain't working - give us details and what errors messages there were when it happened.

#10 I think this was the page Dan meant to link to.

#11 Thanks Stefan I will try to actually read the documentation. I made a mistake thinking that the documentation actually came WITH the cvs program. Wysardry thanks for the proper link.
All of this slamming is really helping alot. So since we chose this path lets go over it.

Reference Dan's comment "Procedure B.3. Checkout" Step #3 and change c:\ to some new directory such as "c:\newDirectoryFor1_3_0"

The picture shows "module name and path on server" set to torque should that be changed to Release_1_3_0 torque?

#12 Howard,

No. Torque is the module you want to checkout, and Release_1_3_0 is the branch. Click on "Checkout Options".

In there, you will find "By revision/branch/tag". Put Release_1_3_0 in there, if that's the release you want to use. Then head to globals and put TCP/IP compression to 3.

That should do it.

#13 Wysardry - Thanks. I should have tried my link after I posted it. My Bad.

#14 What I ment was:

Where is "Local Folder To Checkout to:" change that to something else besides "c:\" If you always leave it the default (C:\) it will check out torque in a directory called "c:\torque". Any other check outs will cause that directory to be over written.

So when you do a check out change the "c:\" to some other folder besides what you are using. That way you will not overwrite what you are using.

Make sense?

#15

Quote:
Yes wincvs is what I have there is another?

Yes, but WinCVS is what GG recommends and has docs for. It is also what I would recommend using.

#16 Ok that worked, thanks all for the help.
This is only the 4th time I've used CVS in 6 months so please forgive my ignorance.