1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Managing Source Code with CVS</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.54"/><LINK
REL="HOME"
TITLE="KDE 2.0 Development"
HREF="index.html"/><LINK
REL="UP"
TITLE="Developer Tools and Support"
HREF="p04.html"/><LINK
REL="PREVIOUS"
TITLE="Summary"
HREF="ch16lev1sec4.html"/><LINK
REL="NEXT"
TITLE="CVS Organization"
HREF="ch17lev1sec2.html"/><META
HTTP-EQUIV="Content-Style-Type"
CONTENT="text/css"/><LINK
REL="stylesheet"
HREF="kde-common.css"
TYPE="text/css"/><META
HTTP-EQUIV="Content-Type"
CONTENT="text/html; charset=iso-8859-1"/><META
HTTP-EQUIV="Content-Language"
CONTENT="en"/><LINK
REL="stylesheet"
HREF="kde-localised.css"
TYPE="text/css"
TITLE="KDE-English"/><LINK
REL="stylesheet"
HREF="kde-default.css"
TYPE="text/css"
TITLE="KDE-Default"/></HEAD
><BODY
CLASS="chapter"
LINK="#336699"
VLINK="#336699"
ALINK="#336699"
BGCOLOR="#FFFFFF"
><DIV
ALIGN="RIGHT"
CLASS="NAVBAR"
><P
><A
HREF="ch16lev1sec4.html"
>Prev</A
> <A
HREF="ch17lev1sec2.html"
>Next</A
> <A
HREF="index.html"
>Table of Contents</A
></P
></DIV
><DIV
CLASS="chapter"
><H1
><A
NAME="ch17"
>Chapter 17. Managing Source Code with CVS</A
></H1
><P
><I
CLASS="emphasis"
>By David Sweet</I
></P
><DIV
CLASS="highlights"
><A
NAME="AEN24530"
></A
><P
><B
>In This Chapter</B
></P
><UL
COMPACT="COMPACT"
><LI
STYLE="list-style-type: disc"
><P
><I
CLASS="emphasis"
><A
HREF="ch17.html#ch17lev1sec1"
>What is CVS?</A
></I
></P
></LI
><LI
STYLE="list-style-type: disc"
><P
><I
CLASS="emphasis"
><A
HREF="ch17lev1sec2.html"
>CVS Organization</A
></I
></P
></LI
><LI
STYLE="list-style-type: disc"
><P
><I
CLASS="emphasis"
><A
HREF="ch17lev1sec3.html"
>Accessing Source Code in CVS</A
></I
></P
></LI
><LI
STYLE="list-style-type: disc"
><P
><I
CLASS="emphasis"
><A
HREF="ch17lev1sec4.html"
>Installing and Using CVSup</A
></I
></P
></LI
><LI
STYLE="list-style-type: disc"
><P
><A
HREF="ch17lev1sec5.html"
><I
CLASS="emphasis"
>Installing and Using</I
> <TT
CLASS="literal"
>cvs</TT
></A
></P
></LI
></UL
></DIV
><P
>The open nature of the KDE project is reflected not only in the fact that the source code is freely distributed, but in the way it is distributed. The project uses CVS, the Concurrent Versions System, to maintain a source-code repository and keep the most up-to-date versions of the development code continuously available for download by interested parties.</P
><DIV
CLASS="section"
><TABLE
WIDTH="100%"
CELLPADDING="0"
CELLSPACING="0"
BORDER="0"
ALIGN="CENTER"
><TR
><TD
WIDTH="90%"
><H1
CLASS="section"
><A
NAME="ch17lev1sec1"
>17.1. What Is CVS?</A
></H1
><P
>CVS, the Concurrent Versions System, is used by the KDE project to manage the KDE source code—source code that is being developed by programmers around the world. The official version of the code is kept on the CVS server. KDE developers can download the portions of code that they are interested in, make changes, and upload the modified code to the server using the <TT
CLASS="literal"
>cvs</TT
> utility.</P
><P
>CVS is released under the GNU General Public License, the same license used by KDE applications. Information about CVS is available from <A
HREF="http://www.cyclic.com/"
TARGET="_top"
>http://www.cyclic.com/</A
>. You may also find links to source and binary distributions there, although the CVS client, <TT
CLASS="literal"
>cvs</TT
>, is included in popular Linux distributions and may already be on your system.</P
><P
>The features offered by CVS are appropriate for distributed computing. When users wish to make changes to files, the system saves only the changes the user has made rather than replacing the original file. Every change to a file increments its version number. This means that changes can be reversed. It also means that a virtual snapshot of the source code can be saved with minimal effort; CVS needs to keep a record only of the current version numbers for the files included in the snapshot. The snapshot can then be accessed by reverting all the files to their recorded version numbers. CVS can also maintain more than one development <SPAN
CLASS="QUOTE"
>"branch"</SPAN
> using this versioning system so that multiple versions of a piece of software can be developed in parallel.</P
><P
>Because it makes the process of distributed development simpler, CVS is used by many free software projects other than KDE. The list includes GIMP, Mozilla, XEmacs, Python, and DES Cracker.</P
><DIV
CLASS="section"
><TABLE
WIDTH="100%"
CELLPADDING="0"
CELLSPACING="0"
BORDER="0"
ALIGN="CENTER"
><TR
><TD
WIDTH="90%"
><H2
CLASS="section"
><A
NAME="ch17lev2sec1"
>17.1.1. The Role of CVS in the KDE Project</A
></H2
><P
>The core KDE code is kept in CVS (note that the term <SPAN
CLASS="QUOTE"
>"CVS"</SPAN
> is used colloquially to refer to the source-code repository as well as the software used to maintain it). This includes the KDE libraries and applications distributed with KDE. Also in CVS are KOffice, an office suite, KLyX, a GUI for the LaTeX typesetting system, and applications being developed for future versions of KDE.</P
><P
>The KDE CVS is also used to maintain two KDE Web sites, <A
HREF="http://www.kde.org"
TARGET="_top"
>http://www.kde.org</A
>, and <A
HREF="http://developer.kde.org"
TARGET="_top"
>http://developer.kde.org</A
>. Keeping the Web site in CVS allows developers to add and update documentation. Having many maintainers means that the Web site can be kept larger and more up-to-date.</P
><P
>This same philosophy applies to the source code (indeed, the primary function of CVS is to maintain software). If you have many programmers downloading, examining, improving, and debugging the most current source, the code improves and everyone benefits. This may lead to some duplicated effort or occasional source-code conflicts because more than one developer may have a piece of code checked out at one time. Experience has shown that these small problems associated with having many developers are more than made up for by the large volume of high-quality code that is produced.</P
></TD
><TD
WIDTH="10%"
VALIGN="BOTTOM"
ALIGN="CENTER"
><ANNMARK
NAME="ch17lev2sec1"/></TD
></TR
><ANNOTATION
NAME="ch17lev2sec1"
TITLE="The Role of CVS in the KDE Project"/></TABLE
></DIV
></TD
><TD
WIDTH="10%"
VALIGN="BOTTOM"
ALIGN="CENTER"
><ANNMARK
NAME="ch17lev1sec1"/></TD
></TR
><ANNOTATION
NAME="ch17lev1sec1"
TITLE="What Is CVS?"/></TABLE
></DIV
></DIV
><DIV
ALIGN="RIGHT"
CLASS="NAVBAR"
><P
><A
HREF="ch16lev1sec4.html"
>Prev</A
> <A
HREF="ch17lev1sec2.html"
>Next</A
> <A
HREF="index.html"
>Table of Contents</A
></P
></DIV
><HR
WIDTH="100%"
SIZE="2"
ALIGN="CENTER"
NOSHADE="NOSHADE"/></BODY
></HTML
>
|
