|
|
e935c3 |
|
|
|
ae52cb |
<sect1 id="repository-usage-section-5" xreflabel="Connection between directories" label="3.5">
|
|
|
e935c3 |
|
|
|
e935c3 |
<title>Connection between directories</title>
|
|
|
e935c3 |
|
|
|
ca81f7 |
<para>In order for automation scripts to produce content inside
|
|
|
ca81f7 |
working copies of CentOS Artwork Repository, it is required that
|
|
|
ca81f7 |
all work lines be connected somehow. Using this connection,
|
|
|
ca81f7 |
automation scripts can know where to retrive the information they
|
|
|
ca81f7 |
need to work with (e.g., design model, translation messages,
|
|
|
ca81f7 |
output locations, etc.). This connection is built using two path
|
|
|
ca81f7 |
constructions named <emphasis>master paths</emphasis> and
|
|
|
ca81f7 |
<emphasis>auxiliar paths</emphasis>.</para>
|
|
|
ca81f7 |
|
|
|
ca81f7 |
<para>The master path points only to directories that contain
|
|
|
e935c3 |
source files (e.g., SVG files) required to produce base content
|
|
|
e935c3 |
(e.g., PNG files) through automation scripts. Each master path
|
|
|
e935c3 |
inside the repository may have several auxiliar paths associated,
|
|
|
ca81f7 |
but auxiliar paths can only have one master path associated.
|
|
|
ca81f7 |
Master paths are organized under
|
|
|
ca81f7 |
class="directory">trunk/Identity/Models</filename> directory
|
|
|
ca81f7 |
structure and auxiliar paths under
|
|
|
ca81f7 |
class="directory">trunk/Identity/Images</filename>,
|
|
|
ca81f7 |
class="directory">trunk/Locales</filename> and
|
|
|
ca81f7 |
class="directory">trunk/Manuals</filename> directory
|
|
|
ca81f7 |
structures.</para>
|
|
|
e935c3 |
|
|
|
e935c3 |
<para>The auxiliar paths can point either to directories or files.
|
|
|
e935c3 |
When an auxiliar path points to a directory, that directory
|
|
|
e935c3 |
contains information that modifies somehow the content produced
|
|
|
e935c3 |
from master paths (e.g., translation messages) or provides the
|
|
|
e935c3 |
output information required to know where to store the content
|
|
|
e935c3 |
produced from master path. When an auxiliar path points to a
|
|
|
e935c3 |
file, that file has no other purpose but to document the master
|
|
|
e935c3 |
path it refers to.</para>
|
|
|
e935c3 |
|
|
|
ca81f7 |
<para>The relationship between auxiliar paths and master paths is
|
|
|
ca81f7 |
realized by combining the master path itself and the second level
|
|
|
ca81f7 |
directory structures of the repository. The master path is
|
|
|
ca81f7 |
considered the path identifier and the second level directory
|
|
|
ca81f7 |
structure taken from the repository is considered the common part
|
|
|
ca81f7 |
of the path where the path identifier is appended to.</para>
|
|
|
ca81f7 |
|
|
|
ae52cb |
</sect1>
|