CVS Quickstart: A Short guide to using CVS on a networked system | ||
---|---|---|
<<< Previous | Next >>> |
Your now ready to start some real work.
The first thing you will need to do is set up a directory in some quiet spot where you can hold your working copy of the source code and have some room and permissions to try stuff out.
There is a "Gotcha" you should know about: Don't build your working directory inside your LOCAL cvs repository.. You can do this but why make life more complex than it needs be? Just make a fresh directory somewhere clean under your HOME directory. |
cd to your new tenforty/CVS-work directory and with your Internet connection all warmed up, issue the following (all one line):
cvs -z3 -d:ext:Login-Name@cvs.tenforty.sourceforge.net:/cvsroot/tenforty co tenforty-example |
Substitute the head directory name of the branch of the CVS Tree you would like for tenforty-example.
What will happen goes like this:
CVS builds a copy of the directory structure beneath wherever you issued the command from.
Each of those directories will include a CVS sub directory with its own admin stuff (you don't need to touch these and they are never included in builds or whatever unless...) It then fills these directories with the files that should be there, and logs this in those subdirectories - and so on.
This is your working copy of the tenforty-example source. Go for it it's all yours, do your worst...have fun.
<<< Previous | Home | Next >>> |
Tell CVS where the Source Repository is | Hack |