|
|
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>
|
|
|
e4773a |
The first level of directories inside &TCAR; provides
|
|
|
e4773a |
organization through a convenctional
|
|
|
e4773a |
class="directory">trunk/</filename>,
|
|
|
e4773a |
class="directory">branches/</filename> and
|
|
|
cd4f82 |
class="directory">tags/</filename> layout. As proposition we
|
|
|
e4773a |
are assuming that:
|
|
|
011179 |
</para>
|
|
|
011179 |
|
|
|
e4773a |
<itemizedlist>
|
|
|
e4773a |
<listitem>
|
|
|
e4773a |
<para>
|
|
|
e4773a |
The <filename class="directory">trunk/</filename>
|
|
|
e4773a |
directory is where development changes take place.
|
|
|
e4773a |
</para>
|
|
|
e4773a |
</listitem>
|
|
|
e4773a |
|
|
|
e4773a |
<listitem>
|
|
|
e4773a |
<para>
|
|
|
e4773a |
The <filename class="directory">branches/</filename>
|
|
|
e4773a |
directory is where maintainance changes take place.
|
|
|
e4773a |
</para>
|
|
|
e4773a |
</listitem>
|
|
|
e4773a |
|
|
|
e4773a |
<listitem>
|
|
|
e4773a |
<para>
|
|
|
e4773a |
The <filename class="directory">tags/</filename> directory
|
|
|
e4773a |
is where final releases take place.
|
|
|
e4773a |
</para>
|
|
|
e4773a |
</listitem>
|
|
|
e4773a |
</itemizedlist>
|
|
|
e4773a |
|
|
|
011179 |
<para>
|
|
|
e4773a |
The second level of directories inside &TCAR; provides
|
|
|
e4773a |
organization for different work lines, as described in
|
|
|
e4773a |
linkend="repo-convs-worklines" />. All other subsequent
|
|
|
e4773a |
directory levels from third level on exist to organize
|
|
|
e4773a |
specific concepts related to the work line they belong to.
|
|
|
011179 |
</para>
|
|
|
3c5068 |
|
|
|
3c5068 |
</sect1>
|