technical article
:: From Teamsource to WinCVS
Author: MusicWind
Version: 1.0
Japanese issue: 2004-7-2
■ Amendment
Amendment
Revision date
Reviewer
MusicWind
o Create this document;
o MusicWind reserves the right to make a copy.
2004-7-2
1 Remote TEAMSOURCE The first version of the management tool used after the work is TeamSource. Because it is a delphi installation package, it will be used in hand. First, use the version of Delphi 5.0, and later discovered the updated version from the installation package of Delphi 6.0, that is, Build 6.0.0.0, so I used it for 3 years. At that time, use TeamSource, regardless of documentation, code, program, rar, as long as it is a file, throw it into TeamSource. Getting a hard drive that stores TeamSource is not enough. The most inconvenient to use TeamSource is unstable - not an exception to exit, that is, let me lose data for no reason, or because of several clients, the server time has different versions. Ugh! Just before months, forced various situations, we finally gave up the use of TeamSource, in which we were installing CVSNT on a Win2000 Server, then use WinCVS on the client. There is a saying that there is no hard work. We make a small summary of the functionality of TeamSource and the existing problems, and it is also a small memory of it! 1.1 Features and use TeamSource features: n allows Checkin and Checkout to support files for different versions of the file; the comparison function of local and remote differences (built-in, a convenient source code comparison tool, just some fonts are somewhat ugly); n has new The file is checked by checkin; N can filter files to be processed according to the file extension; N the entire project's historical log view (record the actions of the server, such as Checkin, delete, etc.); N provides two views , Remote and local. By remote view, directly view and access content on the remote server; on the bottom view, you can perform Checkin, Checkout, Delete, Remove, etc. n The current usage version of the file can be set in the remote view; the deployment of TeamSource: n simple and convenient, dependent on the network file sharing of the operating system, does not require the server; N users only need to install the TeamSource program, and by setting the same project Documents can be used to manage; TeamSource's technical implementation: n With network file sharing, and control lock via a Lock.dat; each version of the n file is compressed in. Z file; 1.2 tears Say goodbye Teamsource Question: N uses a large lock, only one person is only one at the same time, does not support multiple people at the same time of the catalog CHECKIN; N procedures are unstable, often ACCESS VIOLATION errors - this is the first big crime! Moreover, the series of TeamSource is no longer upgraded! (It seems that there is a new TeamSource for web / .net? But never seen) N does not support version branch (maybe I am aloud); N does not support version tags, do not support baseline management.
You can only depend on time to string together in a project; n Remote View: Directory's include, Exclude settings can not take effect in subdirectory, must be manually set; n Due to include the directory of include and Exclude issues, It is easy to cause the document that cannot be checked in, that is, by refreshing in the local view but does not detect the file that needs Check IN. This is the second major sin; Therefore, TeamSource is an extension of all files at Checkin as an Include. The content, the next time you add other types of files, you cannot automatically detect, such as manually adding an extension name or directly adding a *. *. n ..., a word is difficult! 2 Get into CVS Coursses 2.1 Overview CVS is a cross-platform parallel version management tool. Divide the server and clients are divided. The server supports Unix, Linux, Windows and more. Under Windows, the client is a console program. The WinCVS here is a CVS client with a good user interface after encapsulation of CVS. The following main talks about some concepts and features in WinCvs in WinCVS in WinCVS to help the use of TeamSource users more quickly and master WinCVS use (as examples of WinCVS 1.3.17.2 Beta 17 Build 2). Since the use time is not long, the following must have many omissions and errors, please don't finish correct. 2.2 Contrast use Please allow me to use the TeamSource user's inertial thinking to understand CVS (愧, so far, I just use this point of function - although I have learned these pains). Sequence number category TeamSource WinCVS 1.
Basic concepts and terms DO IT and Commit TeamSource support two phases, that is, the related files are first tagged (Copy, Checkin, Merge, Delete From Local, Remove from Project), then execute it using "Do IT". WinCVS uses a similar practice. For local files, there are two types of remodes and adds, followed by COMMIT. Use the UPDATE function to implement similar features of TeamSource. 2.
Basic concepts and terminology refresh local views, Refresh function query update feature 3.
Operation The local new directory and file submitted to the server in the local view, select Refresh; then TeamSource will prompt the file to be submitted in the "Recommented Changes to Remote Project" column on the right. At this point, all files are selected, click Right click Check IN or "Do IT" one-time submission. Select the directory where you are located, you will set the filter to view the status of modifications and updates. And open the Flat Mode. At this point, WinCVS will search for qualified files in the specified directory and display in the workspace. Select related files in batches according to different directories (when the operation object exceeds a directory, "add" or "add binary" or "add unicode 'is added. Then all modified files will be selected in one time. Perform commit. 4.
Operation After modifying the local file, update this in the local view and select the file, check in. Select the directory where the file is located, it will be discovered that the file has been marked as Modified. At this time, check the file, and COMMIT. 5.
The latest version of the download server can automatically create a local directory based on the remote directory structure. After downloading the server version, the version of the local conflict is lost (covered). The local directory cannot be created automatically according to the remote directory structure. The "Create Missing Directory ..." option is required to open the "Create Missing Directory ..." in the Options window pop-up in the Update action. After downloading the server version, WinCVS automatically saves local changes to the name of the file. 6. Operation Wash Local Change Scenario 1: Delete local files, then re-acquire files from the server; Scenario 2: Abandon checkin operation, move the related file to the Recommented Changes to Local Project box and perform "Copy" operation. Check related files, execute Update, open the "Get Clean Copy" option in Options, then OK. Manually delete CVS auto-saved local backup files (after selecting, press DEL ").
2.3 Frequently Asked Questions Solution N Waiting for
LOCK
Possible reasons: Other people are in the process process, forcibly exit? Solution: Log in to the computer of the CVS server, enter the cvsroot / cvsroot directory, delete files that headed with "# cvs.lock", "# cvs.rfl", "# cvs.wfl". However, before doing these operations, be sure to confirm that no one really operate in the implementation of cvs, otherwise the consequences could be unpredictable (from "cvs Nightly Build and technology", author: YANG Jin Fang, Tsinghua University Publishing House). n Commit or modify the state, but the result of the command execution is 0 possible reasons: file time change, but content unconverted solution: Force Checkin, in the option window Option "force" tick, as shown: N ourselves Is user A, but the commit operation prompts to use another user name through authentication? Possible cause: From another colleague (user), copy the files in a directory, and try members of a file in this directory. Since CVS automatically logs a username in a root file called CVS, there is a login error. Workaround: Open the same-level CVS directory in the directory where this file (first open Windows view options, set the hidden directory to view hidden directories), change the username in the root file and the UserName used in CVS. n clearly changed the document changed, is it unable to add? Possible reasons: Other users have just had a version of the file before you have just called; solution: Re-update. Culture
