|
|
de4714 |
<chapter id="repo-repoconvs-layout">
|
|
|
054a7b |
|
|
|
9c6207 |
<title>Repository Layout</title>
|
|
|
054a7b |
|
|
|
054a7b |
<para>
|
|
|
3abc34 |
&TCAR; is supported by
|
|
|
3abc34 |
url="http://subversion.tigris.org/">Subversion</ulink>, a
|
|
|
3abc34 |
version control system which allows you to keep old versions
|
|
|
3abc34 |
of files and directories (usually source code), keep a log of
|
|
|
3abc34 |
who, when, and why changes occurred, etc., like CVS, RCS or
|
|
|
3abc34 |
SCCS.
|
|
|
3abc34 |
</para>
|
|
|
3abc34 |
|
|
|
3abc34 |
<para>
|
|
|
3abc34 |
When using Subversion there is one <quote>source
|
|
|
3abc34 |
repository</quote> and many <quote>working copies</quote> of
|
|
|
3abc34 |
that source repository. The working copies are independent one
|
|
|
3abc34 |
another, can be distributed all around the world and provide a
|
|
|
3abc34 |
local place for designers, documentors, translators and
|
|
|
3abc34 |
programmers to perform their work in a descentralized way.
|
|
|
3abc34 |
The source repository, on the other hand, provides a central
|
|
|
3abc34 |
place for all independent working copies to interchange data
|
|
|
3abc34 |
and provides the information required to permit extracting
|
|
|
3abc34 |
previous versions of files at any time.
|
|
|
3abc34 |
</para>
|
|
|
3abc34 |
|
|
|
3abc34 |
<para>
|
|
|
978692 |
The first level of directories in the repository provides
|
|
|
978692 |
organization through a convenctional <quote>trunk</quote>,
|
|
|
978692 |
<quote>branches</quote> and <quote>tags</quote> layout. In
|
|
|
978692 |
this configuration the
|
|
|
978692 |
class="directory">trunk</filename> directory is where main
|
|
|
978692 |
changes take place, the
|
|
|
978692 |
class="directory">tags</filename> directory is where frozen
|
|
|
978692 |
copies of <filename class="directory">trunk</filename> changes
|
|
|
978692 |
are placed in for releasing, and the
|
|
|
978692 |
class="directory">branches</filename> directory is an
|
|
|
978692 |
intermediate place between
|
|
|
978692 |
class="directory">trunk</filename> and
|
|
|
978692 |
class="directory">tags</filename> states where changes take
|
|
|
978692 |
place before being merged into
|
|
|
978692 |
class="directory">trunk</filename> and finally released into
|
|
|
978692 |
<filename class="directory">tags</filename>.
|
|
|
978692 |
</para>
|
|
|
978692 |
|
|
|
978692 |
<para>
|
|
|
978692 |
The second level of directories in the repository provides
|
|
|
978692 |
organization for each work line described in
|
|
|
de4714 |
linkend="repo-worklines" />.
|
|
|
978692 |
</para>
|
|
|
978692 |
|
|
|
978692 |
<para>
|
|
|
978692 |
All other subsequent levels of directories in the repository,
|
|
|
978692 |
from third level on, are created to organize specific concepts
|
|
|
de4714 |
related to the work line they are in.
|
|
|
054a7b |
</para>
|
|
|
33f520 |
|
|
|
de4714 |
&repo-layout-filenames;
|
|
|
de4714 |
&repo-layout-relbdirs;
|
|
|
de4714 |
&repo-layout-syncpaths;
|
|
|
de4714 |
&repo-layout-extending;
|
|
|
054a7b |
|
|
|
9c6207 |
</chapter>
|