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
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
|
/*
* Copyright (c) 1992, Brian Berliner and Jeff Polk
* Copyright (c) 1989-1992, Brian Berliner
*
* You may distribute under the terms of the GNU General Public License as
* specified in the README file that comes with the CVS 1.4 kit.
*
* This file holds (most of) the configuration tweaks that can be made to
* customize CVS for your site. CVS comes configured for a typical SunOS 4.x
* environment. The comments for each configurable item are intended to be
* self-explanatory. All #defines are tested first to see if an over-riding
* option was specified on the "make" command line.
*
* If special libraries are needed, you will have to edit the Makefile.in file
* or the configure script directly. Sorry.
*/
/*
* CVS provides the most features when used in conjunction with the Version-5
* release of RCS. Thus, it is the default. This also assumes that GNU diff
* Version-1.15 is being used as well -- you will have to configure your RCS
* V5 release separately to make this the case. If you do not have RCS V5 and
* GNU diff V1.15, comment out this define. You should not try mixing and
* matching other combinations of these tools.
*/
#ifndef HAVE_RCS5
#define HAVE_RCS5
#endif
/*
* If, before installing this version of CVS, you were running RCS V4 AND you
* are installing this CVS and RCS V5 and GNU diff 1.15 all at the same time,
* you should turn on the following define. It only exists to try to do
* reasonable things with your existing checked out files when you upgrade to
* RCS V5, since the keyword expansion formats have changed with RCS V5.
*
* If you already have been running with RCS5, or haven't been running with CVS
* yet at all, or are sticking with RCS V4 for now, leave the commented out.
*/
#ifndef HAD_RCS4
/* #define HAD_RCS4 */
#endif
/*
* For portability and heterogeneity reasons, CVS is shipped by default using
* my own text-file version of the ndbm database library in the src/myndbm.c
* file. If you want better performance and are not concerned about
* heterogeneous hosts accessing your modules file, turn this option off.
*/
#ifndef MY_NDBM
#define MY_NDBM
#endif
/*
* The "diff" program to execute when creating patch output. This "diff"
* must support the "-c" option for context diffing. Specify a full
* pathname if your site wants to use a particular diff. If you are
* using the GNU version of diff (version 1.15 or later), this should
* be "diff -a".
*
* NOTE: this program is only used for the ``patch'' sub-command (and
* for ``update'' if you are using the server). The other commands
* use rcsdiff which will use whatever version of diff was specified
* when rcsdiff was built on your system.
*/
#ifndef DIFF
#define DIFF "/usr/local/bin/diff -a"
#endif
/*
* The "grep" program to execute when checking to see if a merged file had
* any conflicts. This "grep" must support a standard basic
* regular expression as an argument. Specify a full pathname if your site
* wants to use a particular grep.
*/
#ifndef GREP
#define GREP "grep"
#endif
/*
* The "patch" program to run when using the CVS server and accepting
* patches across the network. Specify a full pathname if your site
* wants to use a particular patch.
*/
#ifndef PATCH_PROGRAM
#define PATCH_PROGRAM "patch"
#endif
/*
* By default, RCS programs are executed with the shell or through execlp(),
* so the user's PATH environment variable is searched. If you'd like to
* bind all RCS programs to a certain directory (perhaps one not in most
* people's PATH) then set the default in RCSBIN_DFLT. Note that setting
* this here will cause all RCS programs to be executed from this directory,
* unless the user overrides the default with the RCSBIN environment variable
* or the "-b" option to CVS.
*
* If you use the password-authenticating server, then you need to
* make sure that the server can find the RCS programs to invoke them.
* The authenticating server starts out running as root, and then
* switches to run as the appropriate user once authentication is
* complete. But no actual shell is ever started by that user, so the
* PATH environment variable may not contain the directory with the
* RCS binaries, even though if that user logged in normally, PATH
* would include the directory.
*
* One way to solve this problem is to set RCSBIN_DFLT here. An
* alternative is to make sure that root has the right directory in
* its path already. Another, probably better alternative is to
* specify -b in /etc/inetd.conf.
*
* This define should be either the empty string ("") or a full pathname to the
* directory containing all the installed programs from the RCS distribution. */
#ifndef RCSBIN_DFLT
#define RCSBIN_DFLT ""
#endif
/*
* The password-authenticating server creates a temporary checkout of
* the affected files. The variable TMPDIR_DFLT (or even better, the
* command-line option "-T" in the line for CVS in /etc/inetd.conf)
* can be used to specify the used directory. This directory will
* also be used for other temporary files.
*/
#ifndef TMPDIR_DFLT
#define TMPDIR_DFLT "sys$scratch"
#endif
/*
* The default editor to use, if one does not specify the "-e" option to cvs,
* or does not have an EDITOR environment variable. I set this to just "vi",
* and use the shell to find where "vi" actually is. This allows sites with
* /usr/bin/vi or /usr/ucb/vi to work equally well (assuming that your PATH
* is reasonable).
*/
#ifndef EDITOR_DFLT
#define EDITOR_DFLT ""
#endif
/*
* The default umask to use when creating or otherwise setting file or
* directory permissions in the repository. Must be a value in the
* range of 0 through 0777. For example, a value of 002 allows group
* rwx access and world rx access; a value of 007 allows group rwx
* access but no world access. This value is overridden by the value
* of the CVSUMASK environment variable, which is interpreted as an
* octal number.
*/
#ifndef UMASK_DFLT
#define UMASK_DFLT 002
#endif
/*
* The cvs admin command is restricted to the members of the group
* CVS_ADMIN_GROUP. If this group does not exist, all users are
* allowed to run cvs admin. To disable the cvs admin for all users,
* create an empty group CVS_ADMIN_GROUP. To disable access control for
* cvs admin, comment out the define below.
*/
#ifndef CVS_ADMIN_GROUP
/* #define CVS_ADMIN_GROUP "cvsadmin" */
#endif
/*
* The Repository file holds the path to the directory within the source
* repository that contains the RCS ,v files for each CVS working directory.
* This path is either a full-path or a path relative to CVSROOT.
*
* The only advantage that I can see to having a relative path is that One can
* change the physical location of the master source repository, change one's
* CVSROOT environment variable, and CVS will work without problems. I
* recommend using full-paths.
*/
#ifndef RELATIVE_REPOS
/* #define RELATIVE_REPOS */
#endif
/*
* When committing or importing files, you must enter a log message.
* Normally, you can do this either via the -m flag on the command line or an
* editor will be started for you. If you like to use logging templates (the
* rcsinfo file within the $CVSROOT/CVSROOT directory), you might want to
* force people to use the editor even if they specify a message with -m.
* Enabling FORCE_USE_EDITOR will cause the -m message to be appended to the
* temp file when the editor is started.
*/
#ifndef FORCE_USE_EDITOR
/* #define FORCE_USE_EDITOR */
#endif
/*
* When locking the repository, some sites like to remove locks and assume
* the program that created them went away if the lock has existed for a long
* time. This used to be the default for previous versions of CVS. CVS now
* attempts to be much more robust, so lock files should not be left around
* by mistake. The new behaviour will never remove old locks (they must now
* be removed by hand). Enabling CVS_FUDGELOCKS will cause CVS to remove
* locks that are older than CVSLCKAGE seconds.
* Use of this option is NOT recommended.
*/
#ifndef CVS_FUDGELOCKS
/* #define CVS_FUDGELOCKS */
#endif
/*
* When committing a permanent change, CVS and RCS make a log entry of
* who committed the change. If you are committing the change logged in
* as "root" (not under "su" or other root-priv giving program), CVS/RCS
* cannot determine who is actually making the change.
*
* As such, by default, CVS disallows changes to be committed by users
* logged in as "root". You can disable this option by commenting
* out the lines below.
*/
#ifndef CVS_BADROOT
#define CVS_BADROOT
#endif
/*
* The "cvs diff" command accepts all the single-character options that GNU
* diff (1.15) accepts. Except -D. GNU diff uses -D as a way to put
* cpp-style #define's around the output differences. CVS, by default, uses
* -D to specify a free-form date (like "cvs diff -D '1 week ago'"). If
* you would prefer that the -D option of "cvs diff" work like the GNU diff
* option, then comment out this define.
*/
#ifndef CVS_DIFFDATE
#define CVS_DIFFDATE
#endif
/*
* Yes, we can do the authenticated client.
*/
#define AUTH_CLIENT_SUPPORT 1
/*
* define this to enable the SETXID support. Probably has no effect on VMS.
*/
#ifndef SETXID_SUPPORT
/* #define SETXID_SUPPORT */
#endif
/*
* If you are working with a large remote repository and a 'cvs checkout' is
* swamping your network and memory, define these to enable flow control.
* You will end up with even less guarantees of a consistant checkout,
* but that may be better than no checkout at all. The master server process
* will monitor how far it is getting behind, if it reaches the high water
* mark, it will signal the child process to stop generating data when
* convenient (ie: no locks are held, currently at the beginning of a
* new directory). Once the buffer has drained sufficiently to reach the
* low water mark, it will be signalled to start again.
* -- EXPERIMENTAL! -- A better solution may be in the works.
* You may override the default hi/low watermarks here too.
*/
#ifndef SERVER_FLOWCONTROL
/* #define SERVER_FLOWCONTROL */
/* #define SERVER_HI_WATER (2 * 1024 * 1024) */
/* #define SERVER_LO_WATER (1 * 1024 * 1024) */
#endif
/* End of CVS configuration section */
/*
* Externs that are included in libc, but are used frequently enough to
* warrant defining here.
*/
#ifndef STDC_HEADERS
extern void exit ();
#endif
#ifndef getwd
extern char *getwd ();
#endif
#define NO_SOCKET_TO_FD 1
#include "vms.h"
|
