Shulou(Shulou.com)06/03 Report--

(1) installation of the software:

1. Software acquisition: CVS is a typical Server/ client software, with UNIX version of CVS, Linux version of CVS, and WINDOWS version of CVS. The downloaded software package already includes the server side and client side, but we usually use the Windows manipulation system in work, so we can download a client software WinCVS of CVS under Windows. The latest version of CVS is available at the following website.

Http://www.cvshome.org

2. Software version: the latest version of CVS under UNIX is cvs-1.11.5.tar.gz.

The client software WinCVS version of CVS under Windows is WinCVS1.3.

3. Installation of software:

Put the cvs-1.11.5.tar.gz you downloaded into a temporary UNIX catalog and enter it.

# gunzip cvs-1.11.5.tar.gz

Get the cvs-1.11.5.tar file after that, and then implement:

# tar xvf cvs-1.11.5.tar

After getting a cvs-1.11.5 catalogue, enter this catalogue and implement the following orders:

#. / configure

# make

# make install

If there is no fault message in the installation process, it is explained that your installation is successful. If there is a mistake, please reflect on your system settings according to the fault information.

The installation of WinCVS1.3, the client software of CVS under Windows, implements the setup.exe file in the source file, and you can specify the installation contents.

(2) setup of the server side of CVS software:

1. After we install this software, we can start to set the server. As usual, CVS runs on UNIX with the authentication action of Pserver as a kind of work. Therefore, you need to make sure that the / etc/services file in the system has an entry for CVS to do things, and add two lines to this file:

Cvspserver 2401/tcp # cvs client/server operations

Cvspserver 2401/udp # cvs client/server operations

2. CVS starts things through inetd. We need to correct the / etc/inetd.conf file and add a statement.

Cvspserver stream tcp nowait root / usr/bin/cvs cvs-- allow-root=/cvsroot pserver

3. To make cvs work properly, it is also necessary to set up a user group cvs for users who need to apply cvs. Then add a user cvsroot to correct the group attributes of user cvsroot and make it a member of cvs.

Groupadd cvs

Useradd-g cvs cvsroot

4. Create a table of contents, name and path arbitrarily. This table of contents is the contents of the user's source code, that is, the user's data inn (repository), which is the core of CVS, so it should be set up in a partition with sufficient space. Here I set up a cvsroot catalog under the root catalog.

# mkdir cvsroot

5. Create an environment variable CVSROOT, which refers to a position that specifies the location of the data inn. If the shell you are applying is csh, you should edit the .cshrc file under your root catalog and add the following statement

Setenv CVSROOT / cvsroot

Note that the path should be the same as the directory path you use as a data inn.

6. Initialize the contents of your data inn

Cvs-d / cvsroot init

7. After initializing the / cvsroot directory, a CVSROOT catalog will occur under the / cvsroot directory. The files under this directory are the settings files of CVS. Several important files are explained as follows:

Checkoutlist supports the remaining management files of the CVSROOT catalog, allowing you to configure information for various CVS orders

When commitinfo orders the implementation of the cvs commit, this document specifies the order to be carried out when the music document is submitted.

Cvswrappers defines that a packaging measure will be implemented when documents are registered or seized.

A script that editinfo allows you to implement after the diary information is recorded before commit orders it to be started.

History tracks all orders that affect the inn

Loginfo is similar to coimmitinfo, but only implemented after the submission of documents.

Modules allows you to say a tag for a set of files, otherwise you must specify the pathname of the cvs inn ($CVSROOT) for each file to be referenced

Nitify monopolizes care from "watch". "watch" is set by "cvs watch add" and "cvs edit"

Rcsinfo specifies a template for the commit log reply.

Taginfo defines the measures implemented after wanton "tag" manipulation.

Readers sets the list of users with read permissions (the system does not have this file by default and must be added manually)

Writers sets the list of users with read and write permissions (the system does not have this file by default and must be added manually)

At this point, the CVS server is set up, and you can apply your CVS server. You can test your CVS server, enter the following instructions to land the CVS server under the command line, and explain that you have landed on the CVS server without reminding any information.

Cvs-d: pserver:cvsroot@192.168.2.52:/cvsroot login

(3) the settings of CVS client software WinCVS:

1. Software analysis: although the CVS software you install on UNIX includes both the server side and the client side, you need to look like those wordy orders when you apply it. Now there is a software WinCVS which is a client software of CVS running under Windows.

2. Software installation: after getting the installation measures of WinCVS, implement the setup.exe file in it and install it to the catalog you specify.

3. Software startup: start-action-GNU-WinCVS1.3-WinCVS

4. Software settings: select Preferences under the Admin menu. Select the "General" page in the pop-up window, and the specific settings are as follows:

Authentication: pserver (the authentication action is pserver, which is the default authentication action)

Path: / cvsroot (path to the data inn on the server)

Host address: 192.168.2.52 (where is the IP of the server)

User name: zdm (user name of the landing server)

CVSROOT: after the above project is completed, this item will be born on its own initiative, so there is no need to set it here.

5. Disable the check boxes in front of the following two items on the "Globals" page

Checkout read-only (if you select this option, all checkout items are read-only)

Prune (remove) empty directory (empty contents are not allowed)

6. On the "WinCVS" page, enter an item on your local computer after "HOME (passwords and ~ / .cvs *". All the check out and check in manipulations you do later are under this item. The "Default viewer used to" setting defaults to the editor.

7. The "Command Dialogs" page does not need to be set up.

(4) after selecting "Admin"-"login", a window will pop up for you to enter the password, so that you can log in to the CVS server. If you see the following message, your landing is successful:

Cvs-Z9 login

Logging in to: pserver:zdm@192.168.2.52:2401/cvsroot

* CVS exited normally with code 0 *

Every time "CVS exited normally with code 0" ends with a non-zero condition, it is always due to landing failure. The manipulation you make on the CVS is not always a fault manipulation at the end of the 0.

(5) the application of WinCVS:

1. Upload (checkin):

Upload a table of contents:

There is an explore page on the left in the middle of the form. Click on it to select the folder you are going to upload. Click creat- >; >; import module from selection in the menu bar, and an import filter form will pop up. If there is a mistake in your file, there will be error or warn symbols in the import filter form. If so, you'd better see what the problem is first.

The next form that pops up is import setting. Fill in the select the module name and path on the remote server with a name, and when your file is uploaded to the server, the cvs server will set up a code base with that name to send the files that have just been uploaded. Keep in mind that the drop-down box does not have any magical function, it can only remember the objects you filled in last time.

Upload a file:

After adding a new document to the mainland incident catalogue, submit it to the action side. First select the file, then click the "add button (Add selected)" in the equipment bar, add the file, and then select submit order "Commit Selection" from the right-click menu.

2. Download (checkout):

Download a catalog:

After the last step of manipulation, you have the source code in the server, and all the trailblazers can get started. Of course, the trailblazer must first download a copy to the mainland to correct it. Set up a mainland event catalogue, create a new catalogue on your hard drive, for example, create a catalogue called "work", which means that this is an event catalogue. Select creat- >; >; checkout module, and the form that appears is checkout setting. Fill in the module name and path on the server with the name of the module you uploaded to the server in the previous step (upload file). Fill in you in Local folder to checkout to

Download a file:

If you do not warn deleted your mainland incident contents of a file, you can select the middle of the form on the left side of a Modules page, select your work Modules, in the right window, right-click to select who you mistakenly deleted the file, select update selection, the CVS server on the files and mainland documents for synchronization and merging, do not need to check any options that appear, directly select "determine".

3. Lock:

As usual, in the project team, the project manager will regularly issue the latest basic version, begging the small members to further develop on this basic version. In the actual work, there will always be some members who complete the work ahead of schedule, and after they submit changes, the latest version will be higher than the basic version of version released by the project manager. Occasionally, some project members will deliberately sometimes correct the basic version and assign it to be submitted to the basic version. If they are allowed to submit corrections, everyone may work in a fundamental version of the fault, and the achievement is unimaginable.

The manipulation of locking files is as follows:

Admin- >; >; comandline in the menu bar, enter this order:

Full name of cvs admin-l version number file

Note that there is no space between-l and the version number.

If you lock in success, there will be the following reminder:

RCS file: / cvs/hrsystem/test/new.txt,v

1.1.2.3 locked

Done

* CVS exited normally with code 0 *

I can only say so much about the introduction of WinCVS on the client side of CVS. There are a lot of raw materials about WinCVS on the Internet, and everyone can check it out.

(6) Analysis of the company's internal CVS account:

The company's internal CVS server has now been set up, on the portal board (192.168.2.52), and a CVS user has been added to each person, the user name is:

Full name of your last name + first letter of your first name

For example: Zhang Daoming's CVS account is zhangdm.

The password is the same as the user name, which is also zhangdm

Now it is the stage of testing and learning the application of CVS. When everyone is more proficient in the application of CVS, it will be transferred from Microsoft Visual SourceSafe to CVS.

(7) it is necessary to install cvs before installing Python-2.2.1.exe.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.