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
280
281
282
283
284
285
|
<html>
<head>
<title>Multi-Tree Projects</title>
</head>
<body>
<a name="Multi-Tree_Projects"></a>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
<h2 align=center>Multi-Tree Projects</h2>
<small>
<b>up: </b><a href="arch.html#arch">arch</a></br>
</small>
<br>
<p>Large projects are often most naturally divided into a number of
independently maintained sub-projects. For example, <code>arch</code>
itself
consists of six separate projects:
</p><pre>
./src
A generic top-level source file for combining
projects.
</pre>
<pre>
./src/arch
arch itself. That is, the `arch' command and all of
the shell scripts that implement it.
</pre>
<pre>
./src/file-utils
Generic utilities for operating on files and
directories.
</pre>
<pre>
./src/ftp-utils
A scriptable FTP client.
</pre>
<pre>
./src/hackerlab
The hackerlab C library.
</pre>
<pre>
./src/text-utils
Generic utilities for operating on text files.
</pre>
<p>In an <code>arch</code>
source tree, each of those sub-directories is a separate
project tree (each has its own <code>{arch}</code>
subdirectory; each was
initialized by the command <code>larch init-tree</code>
; each is in a separate
category in the repository).
</p><p>To put all the pieces together, use the <code>arch</code>
<em>
<a name="index-pt:0"></a>
configuration
commands
</em>
:
</p><p>(TO BE DOCUMENTED:)
</p><p>Config file format, e.g.:
</p><pre>
./configs/regexps.com/devo.arch:
</pre>
<pre>
#
# Check out an arch distribution from the devo branches.
# Latest revisions.
#
</pre>
<pre>
./src lord@regexps.com--2002/package-framework--devo
./src/arch lord@regexps.com--2002/arch--devo
./src/file-utils lord@regexps.com--2002/file-utils--devo
./src/ftp-utils lord@regexps.com--2002/ftp-utils--devo
./src/hackerlab lord@regexps.com--2002/hackerlab--devo
./src/shell-utils lord@regexps.com--2002/shell-utils--devo
./src/text-utils lord@regexps.com--2002/text-utils--devo
</pre>
<p>and
</p><pre>
% larch build-config --help
instantiate a multi-project tree
usage: build-config [options] config-name
</pre>
<pre>
-V --version print version info
-h --help display help
</pre>
<pre>
--silent no output (except odd errors)
--quiet brief output
--report default output
--verbose maximal output
--debug debugging output
-d --dir DIR cd to DIR first
</pre>
<pre>
Build the named configuration based on the specification
in the "configs" subdirectory at the root of the project
tree.
</pre>
<p>and
</p><pre>
% larch update-config --help
</pre>
<pre>
update a multi-project tree
usage: update-config [options] config-name
</pre>
<pre>
-V --version print version info
-h --help display help
</pre>
<pre>
--silent no output (except odd errors)
--quiet brief output
--report default output
--verbose maximal output
--debug debugging output
</pre>
<pre>
-d --dir DIR cd to DIR first
</pre>
<pre>
--force pass the --force flag to update
</pre>
<pre>
Update the named configuration based on the specification
in the "configs" subdirectory at the root of the project
tree.
</pre>
<p>and
</p><pre>
% larch replay-config --help
</pre>
<pre>
replay a multi-project tree
usage: replay-config [options] config-name
</pre>
<pre>
-V --version print version info
-h --help display help
</pre>
<pre>
--silent no output (except odd errors)
--quiet brief output
--report default output
--verbose maximal output
--debug debugging output
</pre>
<pre>
-d --dir DIR cd to DIR first
</pre>
<pre>
Update the named configuration based on the specification
in the "configs" subdirectory at the root of the project
tree.
</pre>
<p>and
</p><pre>
% larch record-config --help
</pre>
<pre>
record a revision-specific configuration
usage: record-config [options] config-name new-config-name
</pre>
<pre>
-V --version print version info
-h --help display help
</pre>
<pre>
--silent no output (except odd errors)
--quiet brief output
--report default output
--verbose maximal output
--debug debugging output
</pre>
<pre>
-d --dir DIR cd to DIR first
</pre>
<pre>
-f --force overwrite an existing config
</pre>
<pre>
Update the named configuration based on the specification
in the "configs" subdirectory at the root of the project
tree.
</pre>
<p>and
</p><pre>
% larch show-config --help
</pre>
<pre>
show the revision frontier of a configuration
usage: show-config [options] config-name
</pre>
<pre>
-V --version print version info
-h --help display help
</pre>
<pre>
--silent no output (except odd errors)
--quiet brief output
--report default output
--verbose maximal output
--debug debugging output
</pre>
<pre>
-d --dir DIR cd to DIR first
</pre>
<pre>
Print the revision frontier specified by the named configuration
in the "configs" subdirectory at the root of the project
tree.
</pre>
<small><i>arch: The arch Revision Control System
</i></small><br>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
</body>
|
