Use notes for wincvs and cvsnt

Use notes for wincvs and cvsnt

Roger Yang

References:
1. simple use of wincvs and cvsnt (1)
Http://www.dingl.com/view.shtml? X H = 211
Simple use of wincvs and cvsnt (2)
Http://www.dingl.com/view.shtml? X H = 212
According to this article, the CVS server is successfully set up on WINXP using cvsnt, and some basic operations on CVs are completed using wincvs.

2. wincvsoperator Manual
Size: 2,991,880 bytes
Wincvs good Entry Manual
:
Invalid connection updated
Http://www.bestsharing.com/files/ms001125101/WinCVSOperatorManual.rar.html

3. cvs .pdf
Size: 1,724,983 bytes
Although the introduction is very simple, the several knowledge points mentioned are very detailed.
:
Invalid connection updated
Http://www.bestsharing.com/files/ms001125092/CVSQuickIntro.rar.html

1. Install the CVS server
Cvsnt 2.0.41a

Install the CVS Client
Python 2.3.4
Wincvs13b17

2. Several working directories to be created on the CVS server and the CVS Client
CVS server:
1. F:/khroot (the root directory that stores the source code)
2. F:/khtemp (directory for storing CVS error information)

CVS client:
1. E:/cvsclient/admin (the administrator working directory can also have multiple working Directories)
2. E:/cvstemp (temporary wincvs directory)

3. Configure the CVS server
1. Set two directories
2. Check box "use local users for pserver..." to select

4. Configure the CVS Client
1. Set cvsroot (key)
: Pserver: Administrator @ server: F:/khroot

The cvsroot string consists of the following items:
Authentication: authentication method. The default value is pserver.
Path: Path of the warehouse on the CVS server. a cvs server can have multiple warehouses. Different warehouses are identified by the warehouse path.
Host address: IP address or domain name of the CVS server
User name, followed by a colon

2. Set the temporary wincvs directory "home"
E:/cvstemp

3. Set the Administrator's working directory
E:/cvsclient/admin

You can have multiple working directories to store modules with different functions. Use the "change location" button on the toolbar to set them.
The module of checkout serves as the sub-directory of the working directory.

4. Set the wincvs plug-in Editor

5. directory permissions in CVS:
1. List of directory permissions supported by the system:
R read permission
W write permission
C. Create and delete permissions
N has no Permissions

2. By default, any user has all permissions for any directory.
Therefore, after creating a new working directory for a user, the administrator needs to manually set the permission for this directory immediately.

6. Administrator tasks and related operations:
1. modify the permissions of the default module (cvsroot management module), and only grant administrator the permissions of RCW.
1. Default checkout module (cvsroot Management Module)

2. Run the following CVS command on the [cvsroot] module:
CVS chacl default: N cancel the default permissions of all users
CVS chacl administrator: RCW sets administrator to have all Permissions
CVS chown administrator changes the owner of [cvsroot]
View the permission status of [cvsroot] using CVS lsacl

2. Create a working directory for common users
1. Modify the modules file under the [cvsroot] module, one user and one module

2. Compile the modules File
[Description of Module 1] [parameter] [relative directory path 1]
[Description of Module 2] [parameter] [relative directory path 2]
...
[Description of Module N] [parameter] [relative directory path N]

For example:
Cvsroot
Jackey working directory-A jackey
_ Docenter

Wincvs can automatically list the modules listed in this file during checkout.
If the module is not listed in this file, you can only manually enter the module name in wincvs.

3. Commit modules File

4. Upload a working directory
Create a working directory for each user under E:/cvsclient/admin
Then import these working Directories
Finally, delete the local working directories.

5. Set the access permissions for the respective directories for each user. Only the user can access their working directories.
1. Check the working directory of each user to the [admin] Directory.

2. Select a user's working directory and run the following CVS command:
CVS chacl default: N cancel the default permissions of all users
CVS chacl Username: RCW sets that the specified user has all Permissions
CVS lsacl: view the permission status of a specified user's working directory

3. add and delete users:
Run the following CVS command:
CVS passwd-a killer: Add a new user [Killer]
CVS passwd-r jackey Killer bound to [Killer] to NT user [jackey]
CVS passwd-x killer: delete a user [Killer]

7. User management principles in the cvsnt system:
1. The cvsnt user is associated with the NT user on the machine where the cvsnt is located.

2. Only administrator users have the right to create and delete users in cvsnt.

3. Create a New CVS user, which must be bound to the NT user on the machine where the cvsnt is located.

4. One NT user can bind multiple CVs users

8. General operations of CVS users in wincvs:
1. log on to the CVS server
Choose admin> login...

2. log out of the CVS server
Choose admin> logout.

3. Import module operations
1. Import the specified directory to become a CVS module:
The module to be imported is actually a directory containing all the files of the project, such as Directory _ docenter
Set the working directory to the parent directory of the module, for example, yang2003.
Right-click the module name (directory name_docenter) to be imported in the [workspace] column on the left, and select import module in the shortcut menu...
Complete the remaining work according to the wizard.

2. Check the module just imported in checkout and set the permission:
After import, you can delete the local directory _ docenter.
In the left-side [workspace] bar, right-click the working directory yang2003 and select the checkout module in the shortcut menu...
Enter the module name_docenter and press "OK" to bring the module _ docenter checkout you just imported to the working directory yang2003.
Select _ docenter in the [workspace] bar on the left, press the shortcut key [Ctrl + L], and execute the following CVS command in sequence to set permissions:
CVS chacl default: N
CVS chacl Yang: RCW
CVS chown Yang
CVS lsacl

3. Checkout specifies the directory method in a module
In the [workspace] bar on the left, right-click the working directory yang2003 and select the checkout module in the shortcut menu...
Enter the module name j2me_prj/ciayhb,
Check out into directory and enter ciayhb in the input box on the right.
(If you select the check box don't shorten module path below, the path j2me_prj/ciayhb will still exist in the ciayhb directory created during checkout)
Press the "OK" button to go to The ciayhb directory in the checkout module j2me_prj under the working directory yang2003, instead of the entire module j2me_prj.

4. Definitions of check boxes in the update Settings dialog box of wincvs
1. Checkout file to standard output
Detect files to standard output

2. Do not recurse into sub-folders
Only update files in the current directory without recursive subdirectories

3. Reset any sticky date/Tag/'-k' options
Reset all pasting date/marker/-K options
Delete the branch/tag to obtain the latest version, which is used to switch from the branch to the trunk

4. Create missing directories that exist in the repository
Create a directory lost in the repository

5. Get the clean copy
Get a clean copy. When a local file is incorrectly modified, you can retrieve the file on the server and overwrite the local file (used when the local file is incorrectly modified ).

5. Add a directory or file to a module
[Add selection] in the menu [modify] is used to add directories and text files.
[Add binary] is used to add binary files.

After adding a file, you need to perform a commit operation. The entire addition operation is complete.

Adding a directory does not require the commit operation

6. retrieve a certain version of a program from the CVS server
In the update options tab of the update Settings dialog box
Select the retrieve rev./Tag/brain check box, and enter a previous version number in the combo box.

7. Obtain the list of modules on the CVS server in two ways:
Both methods do not depend on the modulles file in the cvsroot directory on the CVS server,
Modules not registered in the modules file can also be listed.

1. Choose [admin]-> [admin macros]-> [browse repository folders...]
In the Browse repository folders dialog box, enter cvsroot:
: Pserver: test @ server: e:/cvsroot

(Password is not required, and administrator user is not required)
After selecting a Module Directory, press "checkout..." to export the specified module.

2. Choose [admin]> [admin macros]> [list module contents]
In the title dialog box, enter cvsroot:
: Pserver: Test: test @ server: e:/cvsroot

(The password is required, and the administrator user is not required)

8. Fixed version
Commit file to a specified version
In the commit options Tab Of The commit Settings dialog box,
Select the "Force revision/branch" check box and enter a version number in the combo box that follows.

Corresponding CVS command: CVs commit-M test fixed version to 1.5-R 1.5 New file. DOC (in directory F:/yang2003/_ docenter/tool software /)

9. Track who is editing the file
If a module is checkout in read-only mode, you must notify the CVS server of the file to be edited before editing a file.
The advantage of this is that other developers can track who is editing the corresponding file.

Start editing
Select the file to edit
Click menu [trace]-> [edit selection]
The specified file is removed from the read-only status by wincvs and set to the editing status.

Edited
File specified by commit
The file is set to read-only by wincvs.

Discard Edit
Select the specified file
Click menu [trace]-> [unlock selection]

View the person editing the specified file
Select the specified file
Click [trace]-> [editors]

10. Tag one or more files or directories)
The tag can be used as a reference for the revision.
A special case: tag the entire module to re-construct the current status of the module in the future.
Tag marking time: prior to project release or major modification

Specific operations:
1. Select the directory or file to be tagged.
2. Click [modify]-> [Create a tag on selection...]
3. Enter the tag name in the new tag name input box.
Label naming rules:
It must start with a letter, followed by multiple letters, numbers, minus signs, and underscores. It cannot start with a dot or space.
Two reserved tag names: "head" refers to the latest available version in the library, and "base" refers to the last version from checkout to local.

11. view the file tag and revision status
Select [Status selection] in the file shortcut menu

12. delete files or directories
Delete an object
1. Select an object
2. Click [modify]-> [remove]
3. The commit file is physically deleted locally and marked as "deleted" on the CVS server rather than physically deleted)

The earlier version of the checkout module can still restore the deleted files.

Delete empty directory
1. In the [workspace] box on the left, select the parent directory of the empty directory to be deleted.
2. Right-click "Update selection" in the shortcut menu"
3. Select the check box "prune empty directories" on the "globals" tab of the "update settings" dialog box"
4. Press OK.

13. Branch (Branch)
1. Create a branch
1. Select a directory or file
2. Menu [modify]-> [Create a branch...]
3. Enter the branch name in the "new branch" combo box. (The branch name naming rules are consistent with the standard signature)
4. Select the check box "check that the files are unmodified before tagging "/
5. Press "OK ".

2. Switch to the branch (it can be any of multiple branches)
1. Select a directory or file
2. Menu [modify]-> [update selection...]
3. Select the check box "create missing directories that exist in the repository"
4. Switch to the "update options" tab"
5. Select the check box "retrieve rev./Tag/branch" and enter the branch name in the combo box on the right of the check box.
6. Click "OK ".

3. Switch to the trunk
1. Select a directory or file
2. Menu [modify]-> [update selection...]
3. Select the check box "create missing directories that exist in the repository"
4. Select the check box "Reset any sticky date/Tag/'-k' options"
5. Click "OK ".

4. Merge. Merge the changes to the Branch file to the master file, or vice versa.
1. Switch to the trunk
2. Select a directory or file
3. Menu [modify]-> [update selection...]
4. Select the check box "create missing directories that exist in the repository"
5. Switch to the tab "merge options"
6. Select the check box "only this Rev./Tag" and enter "branch name" in the check box below"
7. Click "OK.

9. CVs terminology
1. repository; root directory of the CVS server. set of modules.
2. Module module; the first sub-directory under the root directory of the CVS server. It is usually used to store all files of a project.
3. Check out; usually refers to the first time an entire module in the repository is exported to the local device.
4. Import: Submit the entire directory structure and create a new module.
5. Release Version of release; version of the entire product.
6. revision Revision; version of a single file. (the version number is always an even number)
7. Tag tag; the symbol name specified for a file set on a development basis. It is used to calibrate specific information.
8. Update updates: download files modified by others from the module and update local copies.
9. Submit the file. Submit the modified file to the module.
10. Branch branch; a separate development line used to isolate modifications. (The Branch version number is always an odd number)