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
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
|
<html>
<head>
<title>Archives</title>
</head>
<body>
<a name="Archives"></a>
<a href="http://www.regexps.com">The Hackerlab at <code>regexps.com</code></a>
<h2 align=center>Archives</h2>
<small>
<b>up: </b><a href="arch.html#arch">arch</a></br>
<b>next: </b><a href="development-paths.html#Development_Paths">Development Paths</a></br>
<b>prev: </b><a href="project-names.html#The_arch_Global_Name-space_of_Projects">The arch Global Name-space of Projects</a></br>
</small>
<br>
<p><a name="index-pt:0"></a>
</p><p>This chapter discusses <em>
<a name="index-pt:1"></a>
archives
</em>
-- places where revisions can stored
and shared. Archives are used to keep a detailed history of how a
project evolves. They are used to help a team of developers stay "in
sync" -- in agreement about what the official, latest revision of a
project really is. Archives are used to help coordinate divergent
development paths (branches) and to merge changes between branches.
</p>
<a name="Archive_Names_Revisited"></a>
<h3 align=center>Archive Names Revisited</h3>
<p>Every archive has a name which <em>should</em> be globally unique. These
names were previously introduced in the context of project names
generally (see <a href="project-names.html#Archive_Names">Archive Names</a>.)
</p><p>To briefly review, an archive name consists of an email address (with
complete hostname), followed by "--", followed by an additional string
of numbers, letters and dashes. Choose an email address which is
exclusively yours (or your project's). That way, your archive name
will be globally unique. Here is an example:
</p><pre>
joe.hacker@gnu.org--test-archive
</pre>
<a name="Creating_a_New_Archive"></a>
<h3 align=center>Creating a New Archive</h3>
<p><a name="index-pt:2"></a>
</p><p>To create a new archive on a local file system, use the <code>make-archive</code>
command:
</p><pre>
% larch make-archive NAME LOCATION
</pre>
<p>The <code>NAME</code>
is the name for the archive. The <code>LOCATION</code>
is a name for
a directory that will be created to hold the archive. For example:
</p><pre>
% larch make-archive \
joe.hacker@gnu.org--test-archive \
~/{test-archive}
</pre>
<a name="Mapping_Archive_Names_to_Locations"></a>
<h3 align=center>Mapping Archive Names to Locations</h3>
<p><a name="index-pt:3"></a>
<a name="index-pt:4"></a>
<a name="index-pt:5"></a>
</p><p><code>arch</code>
maintains a mapping of archive names to archive locations
separately for each user, in the directory <code>~/.arch-params</code>
.
</p><p>You can see the list of archives for which you have a recorded
location by using the <code>archives</code>
command, as in this example:
</p><pre>
% larch archives
joe.hacker@gnu.org--test-archive
/home/joe/{test-archive}
</pre>
<p>The command <code>register-archive</code>
is used to add, remove, or update the
location of an archive:
</p><pre>
% larch register-archive ARCHIVE-NAME LOCATION
</pre>
<p>records a new archive location or changes an old one. The command:
</p><pre>
% larch register-archive -d ARCHIVE-NAME
</pre>
<p>removes the record of an archive location.
</p><p>If you want to know the registered location of a particular archive,
you can use:
</p><pre>
% larch whereis-archive ARCHIVE-NAME
LOCATION
</pre>
<a name="Remote_Archives"></a>
<h3 align=center>Remote Archives</h3>
<p><a name="index-pt:6"></a>
<a name="index-pt:7"></a>
</p><p>If an archive directory is accessible via <code>FTP</code>
, then <code>arch</code>
can
access that archive remotely, simply by specifying an FTP URI for the
archive's location:
</p><pre>
% larch register-archive joe.hacker@gnu.org--test-archive \
ftp://anonymous@ftp.gnu.org/users/joe/{test-archive}
</pre>
<p>The URI can include a password. When <code>arch</code>
saves a location in your
<code>.arch-params</code>
directory, it is made unreadable to anyone but you --
weak security, but security nonetheless.
</p>
<a name="Your_Default_Archive"></a>
<h3 align=center>Your Default Archive</h3>
<p>Using <code>arch</code>
is generally simplified by setting a <em>
<a name="index-pt:8"></a>
default archive
</em>
--
the archive to use by default when no other is specified.
</p><p>The command:
</p><pre>
% larch my-default-archive [options] [archive]
</pre>
<p>can be used to set or check your default archive. (This command was
previously introduced. See <a href="project-names.html#Archive_Names">Archive Names</a>.)
</p><p>In general, <code>arch</code>
sub-commands accept the option <code>-A</code>
to specify a
non-default archive:
</p><pre>
% larch categories -A joe.hacker@gnu.org--test-archive
</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>
|
