blob: 6b821d889a613604843493d997f32cb4c731cab3 (
plain)
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
|
## SECTION=applications
# CVS client/server
menuconfig CVS
tristate
#
# cvs brings its own libz, but the current
# ptxdist patch remove it.
#
select ZLIB
select LIBC_CRYPT
select LIBC_NSL
prompt "cvs "
help
CVS is the Concurrent Versions System. This is a version control system
useful for projects using a central repository to hold files and then
track all changes made to those files.
if CVS
comment "build options ---"
config CVS_CLIENT
bool
select CVS_PSSWRD_CLIENT
prompt "Build cvs client"
help
Include code for running as a remote client
config CVS_PSSWRD_CLIENT
bool
depends on CVS_CLIENT
prompt "Support password authenticated client"
help
Enable pserver as a remote access method in the CVS client
config CVS_SERVER
bool
default y
prompt "Build cvs server"
help
Include code for running as a server
config CVS_FLOW_CONTROL
bool
depends on CVS_SERVER
default y
prompt "Enable server flow control"
help
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
may optionally pass a low water mark in bytes and a high water mark in
bytes, separated by commas. (default is enabled 1M,2M)
config CVS_ENCRYPTION
bool
depends on CVS_SERVER
prompt "Enable encryption"
help
Enable encryption support
config CVS_ROOTCOMMIT
bool
depends on CVS_SERVER
prompt "Allow root commits"
help
Allow the root user to commit files
comment "install options ---"
config CVS_SERVER_POPULATE_CVSROOT
bool
depends on CVS_SERVER
prompt "Populate CVSROOT files"
help
This will install a list of files into target's cvs repository. These files
are supporting files; they do not have to exist for cvs to operate, but they
allow you to make cvs operation more flexible.
Here is the list of files cvs can run on some events:
- commitinfo
- cvsignore
- cvswrappers
- editinfo
- history
- loginfo
- modules
- rcsinfo
- taginfo
and for general configuration:
- config
- passwd
- readers
- writers
PTXdist will copy these files from the active project from projectroot/cvsroot/
into target's file system. Only existing files in projectroot/cvsroot/ will be
copied to /srv/cvsroot/CVSROOT/ (or anywhere you locate the repository). To use
this feature do not leave "cvs' repository" entry empty!
comment "runtime options ---"
config CVS_SERVER_REPOSITORY
string
depends on CVS_SERVER
prompt "cvs' repository"
default "/srv/cvsroot"
help
This will be cvs server's root repository (given to cvs as --allow-root=...).
You must give a path here to use the "Populate CVSROOT files" feature.
choice
prompt "cvs startup type"
depends on CVS_SERVER
config CVS_STARTSCRIPT
bool
prompt "startscript (standalone)"
help
This installs cvs startup script /etc/init.d/cvs. With this
script the cvs server will be started at system startup and
waits for connections
config CVS_INETD
bool
prompt "inetd"
help
Install a inetd rule for cvs. This option adds the following line
to /etc/inetd.conf.d/cvs:
cvs stream tcp nowait root /usr/bin/cvs cvsd -f --allow-root=/srv/cvsroot pserver
Note: You must enable one of the two possible inet daemons:
There is one embedded in busybox and one in packet inetutils.
endchoice
endif
|
