After starting wincvs the first time, set your preferences ...
WinCVS.exe with Kerberos v4 support is available in \\tremont\bin along with the supplemental files that it requires. Map the drive and include it in your path.
After starting wincvs the first time, set your preferences, including the CVSROOT. For now your CVSROOT should be :kserver:cvs.mit.edu:/cvs/pismere-test. And you should be using CVS version 1.9 rather 2.0 for now.
“CvsAdmin -> Preferences”
[pic]
You also need to set the port number to 1999:
[pic]
Since you can not just browse the file system to examine the modules that are available under your repository, you should look at the modules file. You can either check this out to the console window or you can check the file out to disk. (There is an error in the screen shot below. Do you see it?)
[pic]
The screen shot above has an error. The path to the modules file is actually CVSROOT/modules, not CVSROOT\modules. The remote repository is running on UNIX, so you must use the UNIX filename conventions.
Suppose that you wanted to check out everything in the repository. At this time you cannot do this very easily. If you just use the “.” notation to specify everything, this will only work when checking out files to the console window.
[pic]
If you try to check everything out to the disk without some advance preperation you will encounter some problems. First you will get an error message that states, “cvs checkout: cannot open CVS/Entries for reading: No such file or directory
cvs [checkout aborted]: no repository.” To get around this create the missing file and directory.
md CVS
cd CVS
cat con > Entries
^Z
Try checking out “.” again and you will still get an error, “cvs checkout: in directory .:
cvs [checkout aborted]: *PANIC* administration files missing.”
Now create a file named CVS/Repository which contains “/cvs/pismere-test” or “/cvs/pismere” depending on which repository you are working with.
Please note, checking out “.” can take a long time and a lot of disk space. You may want to check out CVSROOT/modules instead.
Things not to do when performing the initial check in:
When you are going to bring a project under CVS you need to perform an import the first time. WinCVS has one dialog box that can be a little misleading at the moment:
[pic]
Be careful with what you type into the “Select the module name and path on the remote server” field. From the caption you might think that the field would expect the same syntax as a module definition line from the modules file.
It doesn’t. It really just creates the top level subdirectory for the module that you are importing. It’s nice to have this be similar or identical to the project, but this is not a requirement.
Do not use any spaces. The server will happily create a directory with a space, but not all of the code in WinCvs and the supplemental files will deal with this correctly; welcome the Hotel California effect, you can check in, but you can’t check out.
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related download
- and resetting the class path
- after starting wincvs the first time set your preferences
- user guide template
- procedure for installation
- knowledge base abila
- to run cadence you just need to have usr local apps bin
- creating a smart document
- unit os4 scheduling and dispatch assignments 2
- installation back out and rollback guide template