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