Tree - centos/artwork-archive - CentOS Git server

centos / artwork-archive

Files

Commit: 33f076a3c571cdcb44aa3cc46c5b5c96e9ae1e63

Blob Blame History Raw

 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
<html>
<!--This manuals documents relevant information regarding the deployment,
organization, and administration of CentOS Artwork Repository.
 
Copyright C 2009-2011 Alain Reguera Delgado
 
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no
Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
copy of the license is included in the section entitled GNU Free
Documentation License.  
-->
<!-- Created on March, 8 2011 by texi2html 1.76 -->
<!--
Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
            Karl Berry  <karl@freefriends.org>
            Olaf Bachmann <obachman@mathematik.uni-kl.de>
            and many others.
Maintained by: Many creative people <dev@texi2html.cvshome.org>
Send bugs and suggestions to <users@texi2html.cvshome.org>
 
-->
<head>
<title>CentOS Artwork Repository: 2.3 The trunk Directory</title>
 
<meta name="description" content="CentOS Artwork Repository: 2.3 The trunk Directory">
<meta name="keywords" content="CentOS Artwork Repository: 2.3 The trunk Directory">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="texi2html 1.76">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">
<!--
@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";
 
a.summary-letter {text-decoration: none}
pre.display {font-family: serif}
pre.format {font-family: serif}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: serif; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: serif; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.sansserif {font-family:sans-serif; font-weight:normal;}
ul.toc {list-style: none}
-->
</style>
 
 
</head>
 
<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">
 
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="repository_6.html#SEC16" title="Previous section in reading order"> &lt; </a>]</td>
<td valign="middle" align="left">[<a href="#SEC18" title="Next section in reading order"> &gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_79.html#SEC416" title="Next chapter"> &gt;&gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
<td valign="middle" align="left">[<a href="repository_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
<td valign="middle" align="left">[<a href="repository_79.html#SEC416" title="Index">Index</a>]</td>
<td valign="middle" align="left">[<a href="repository_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
</tr></table>
<a name="Filesystem-trunk"></a>
<a name="SEC17"></a>
<h2 class="section"> 2.3 The <tt>`trunk'</tt> Directory </h2>
 
 
<a name="SEC18"></a>
<h3 class="subsection"> 2.3.1 Goals </h3>
 
<p>This directory implements the Subversion's trunk concept in a
trunk, branches, tags repository structure.
</p>
 
<a name="SEC19"></a>
<h3 class="subsection"> 2.3.2 Description </h3>
 
<p>The <tt>`trunk/'</tt> directory structure is the main development line
inside the CentOS Artwork Repository. Here is where we produce the
information required by The CentOS Project corporate visual identity.
Additionally, here is where documentation and automation scripts are
conceived to make both understanding and using of CentOS Artwork
Repository easier for everyone.
</p>
<p>The <tt>`trunk/'</tt> directory structure covers the following topics:
</p>
<dl compact="compact">
<dt> <strong>Identity</strong></dt>
<dd><p>This directory organizes the production of images in different formats
and some non-image formats like XHTML and text files, as well. This is
the perfect place to consolidate <em>The CentOS Artwork SIG</em>. If you
are interested in producing art works for The CentOS Project, this
place is for you. 
</p>
<p>See section <a href="repository_8.html#SEC22">The <tt>`trunk/Identity'</tt> Directory</a>, for more information.
</p>
</dd>
<dt> <strong>Documentation</strong></dt>
<dd><p>This directory organizes the production of <em>CentOS Artwork
Repository Manual</em> (i.e., the place where the documentation you are
reading right now is stored in).  If you are interested on improving
The CentOS Artwork Repository Manual, in this place you'll find the
Texinfo documentation structure you need to work with.
</p>
<p>See section <a href="repository_62.html#SEC313">The <tt>`trunk/Manual'</tt> Directory</a>, for more information.
</p>
</dd>
<dt> <strong>Localization</strong></dt>
<dd><p>This directory organizes translation messages specifically produced to
satisfy internationalization needs inside the CentOS Artwork
Repository. This place is perfect to consolidate <em>The CentOS
Translation SIG</em>. If you love translating, you'll find lot of messages
waiting for you to translate here.  
</p>
<p>See section <a href="repository_51.html#SEC258">The <tt>`trunk/Locales'</tt> Directory</a>, for more information.
</p>
</dd>
<dt> <strong>Automation</strong></dt>
<dd><p>This directory organizes the production of <code>centos-art</code>, a
command-line interface specially designed to automate most frequent
tasks in the repository (e.g., image rendition, documenting directory
structures, translating content, etc.).  If you can't resist the idea
of automating repeatable tasks, then take a look here.
</p>
<p>See section <a href="repository_64.html#SEC323">The <tt>`trunk/Scripts'</tt> Directory</a>, for more information.
</p></dd>
</dl>
 
 
<a name="SEC20"></a>
<h3 class="subsection"> 2.3.3 Usage </h3>
 
<p>When we need to create branches or tags, the <tt>`trunk/'</tt> directory
structure is the one used as reference to build them. Take a look at
the following directory structure construction and notice how the
<tt>`/Scripts/Bash/Cli'</tt> string is repeated in the paths and how it is
put on it:
</p>
<dl compact="compact">
<dt> <tt>`trunk/Scripts/Bash/Cli'</tt></dt>
<dd>
<p>This directory structure provides the main development line of the
<tt>`centos-art'</tt> command-line interface written in bash. In this
directory changes may occur pretty fast and in unpredicted ways. This
configuration could provoke that the <tt>`centos-art'</tt> command-line
stop working in a manner unprediceted due the way changes are
introduced to it.
</p>
</dd>
<dt> <tt>`branches/Scripts/Bash/Cli/1'</tt></dt>
<dd>
<p>This directory structure, however, provides an intermediate place for
less unpredicted changes and that way to provide more stability than
<tt>`trunk/'</tt> directory structure is able to provide. 
</p>
<p>Notice that we used a number to identify the branch (the number `1' in
this case).  Changing this number we could create several branches
that could be maintained at the same time to fix specific problems
simultaneausly otherwise difficult to fix in an unpredictable area
like that provided by <tt>`trunk/'</tt> directory structure.  Once the
specific problems has been fixed, the branch is merged into
<tt>`trunk/'</tt> and removed from the repository file system.
</p>
<p>If you are the only person working in the repository, you probably
don't want to worry about creating branches at all and prefer going
straight from trunk to tags. Ask yourself: If I'm the only person
working in the trunk directory structure whom else could introduce
unpredictable changes but myself? In that case, such changes wouldn't
be unpredictable at all, don't you think? 
</p>
</dd>
<dt> <tt>`tags/Scripts/Bash/Cli/1.0'</tt></dt>
<dd>
<p>Instead of removing the branch directory structure from the repository
file system, it could be very convenient to create a check-point in
time with such problems fixed and so providing a predictable release
of the <tt>`centos-art'</tt> command-line interface.
</p>
<p>Notice that we used the number 1.0 to store the tag. These means that
we are creating the tag number 0 from the branch numbered as 1 (i.e.,
the first number before the dot represents the branch number and the
second number after the dot represents the tag number).  
</p>
<p>Using the <tt>`centos-art'</tt> command-line from tags diectory structure
does provide more stable results than those from branches or trunk
directory structures. The tags directory structure doesn't introduce
changes at all, so you are safe to get what you expect after reading
the release notes for that tag. This configuration is not possible
supported on trunk nor branches since they do change through time.
</p></dd>
</dl>
 
<p>It seems to be no other immediate use for this directory but those
described above.
</p>
 
<a name="SEC21"></a>
<h3 class="subsection"> 2.3.4 See also </h3>
 
<table class="menu" border="0" cellspacing="0">
<tr><td align="left" valign="top"><a href="repository_5.html#SEC5">2.1 The <tt>`branches'</tt> Directory</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
</td></tr>
<tr><td align="left" valign="top"><a href="repository_6.html#SEC12">2.2 The <tt>`tags'</tt> Directory</a></td><td>&nbsp;&nbsp;</td><td align="left" valign="top">
</td></tr>
</table>
 
 
 
<table cellpadding="1" cellspacing="1" border="0">
<tr><td valign="middle" align="left">[<a href="#SEC20" title="Previous section in reading order"> &lt; </a>]</td>
<td valign="middle" align="left">[<a href="repository_8.html#SEC22" title="Next section in reading order"> &gt; </a>]</td>
<td valign="middle" align="left"> &nbsp; </td>
<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Beginning of this chapter or previous chapter"> &lt;&lt; </a>]</td>
<td valign="middle" align="left">[<a href="#SEC17" title="Up section"> Up </a>]</td>
<td valign="middle" align="left">[<a href="repository_79.html#SEC416" title="Next chapter"> &gt;&gt; </a>]</td>
</tr></table>
<p>
 <font size="-1">
  This document was generated on <i>March, 8 2011</i> using <a class="www" href="http://texi2html.cvshome.org/"><i>texi2html 1.76</i></a>.
 </font>
 <br>
 
</p>
</body>
</html>

	<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html401/loose.dtd">
	<html>
	<!--This manuals documents relevant information regarding the deployment,
	organization, and administration of CentOS Artwork Repository.

	Copyright C 2009-2011 Alain Reguera Delgado

	Permission is granted to copy, distribute and/or modify this document
	under the terms of the GNU Free Documentation License, Version 1.2 or
	any later version published by the Free Software Foundation; with no
	Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A
	copy of the license is included in the section entitled GNU Free
	Documentation License.
	-->
	<!-- Created on March, 8 2011 by texi2html 1.76 -->
	<!--
	Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
	Karl Berry <karl@freefriends.org>
	Olaf Bachmann <obachman@mathematik.uni-kl.de>
	and many others.
	Maintained by: Many creative people <dev@texi2html.cvshome.org>
	Send bugs and suggestions to <users@texi2html.cvshome.org>

	-->
	<head>
	<title>CentOS Artwork Repository: 2.3 The trunk Directory</title>

	<meta name="description" content="CentOS Artwork Repository: 2.3 The trunk Directory">
	<meta name="keywords" content="CentOS Artwork Repository: 2.3 The trunk Directory">
	<meta name="resource-type" content="document">
	<meta name="distribution" content="global">
	<meta name="Generator" content="texi2html 1.76">
	<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
	<style type="text/css">
	<!--
	@import "/home/centos/artwork/trunk/Identity/Models/Css/Texi2html/common.css";

	a.summary-letter {text-decoration: none}
	pre.display {font-family: serif}
	pre.format {font-family: serif}
	pre.menu-comment {font-family: serif}
	pre.menu-preformatted {font-family: serif}
	pre.smalldisplay {font-family: serif; font-size: smaller}
	pre.smallexample {font-size: smaller}
	pre.smallformat {font-family: serif; font-size: smaller}
	pre.smalllisp {font-size: smaller}
	span.sansserif {font-family:sans-serif; font-weight:normal;}
	ul.toc {list-style: none}
	-->
	</style>


	</head>

	<body lang="en" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#800080" alink="#FF0000">

	<table cellpadding="1" cellspacing="1" border="0">
	<tr><td valign="middle" align="left">[<a href="repository_6.html#SEC16" title="Previous section in reading order"> < </a>]</td>
	<td valign="middle" align="left">[<a href="#SEC18" title="Next section in reading order"> > </a>]</td>
	<td valign="middle" align="left">   </td>
	<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Beginning of this chapter or previous chapter"> << </a>]</td>
	<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Up section"> Up </a>]</td>
	<td valign="middle" align="left">[<a href="repository_79.html#SEC416" title="Next chapter"> >> </a>]</td>
	<td valign="middle" align="left">   </td>
	<td valign="middle" align="left">   </td>
	<td valign="middle" align="left">   </td>
	<td valign="middle" align="left">   </td>
	<td valign="middle" align="left">[<a href="repository.html#SEC_Top" title="Cover (top) of document">Top</a>]</td>
	<td valign="middle" align="left">[<a href="repository_toc.html#SEC_Contents" title="Table of contents">Contents</a>]</td>
	<td valign="middle" align="left">[<a href="repository_79.html#SEC416" title="Index">Index</a>]</td>
	<td valign="middle" align="left">[<a href="repository_abt.html#SEC_About" title="About (help)"> ? </a>]</td>
	</tr></table>
	<a name="Filesystem-trunk"></a>
	<a name="SEC17"></a>
	<h2 class="section"> 2.3 The <tt>`trunk'</tt> Directory </h2>


	<a name="SEC18"></a>
	<h3 class="subsection"> 2.3.1 Goals </h3>

	<p>This directory implements the Subversion's trunk concept in a
	trunk, branches, tags repository structure.
	</p>

	<a name="SEC19"></a>
	<h3 class="subsection"> 2.3.2 Description </h3>

	<p>The <tt>`trunk/'</tt> directory structure is the main development line
	inside the CentOS Artwork Repository. Here is where we produce the
	information required by The CentOS Project corporate visual identity.
	Additionally, here is where documentation and automation scripts are
	conceived to make both understanding and using of CentOS Artwork
	Repository easier for everyone.
	</p>
	<p>The <tt>`trunk/'</tt> directory structure covers the following topics:
	</p>
	<dl compact="compact">
	<dt> <strong>Identity</strong></dt>
	<dd><p>This directory organizes the production of images in different formats
	and some non-image formats like XHTML and text files, as well. This is
	the perfect place to consolidate <em>The CentOS Artwork SIG</em>. If you
	are interested in producing art works for The CentOS Project, this
	place is for you.
	</p>
	<p>See section <a href="repository_8.html#SEC22">The <tt>`trunk/Identity'</tt> Directory</a>, for more information.
	</p>
	</dd>
	<dt> <strong>Documentation</strong></dt>
	<dd><p>This directory organizes the production of <em>CentOS Artwork
	Repository Manual</em> (i.e., the place where the documentation you are
	reading right now is stored in). If you are interested on improving
	The CentOS Artwork Repository Manual, in this place you'll find the
	Texinfo documentation structure you need to work with.
	</p>
	<p>See section <a href="repository_62.html#SEC313">The <tt>`trunk/Manual'</tt> Directory</a>, for more information.
	</p>
	</dd>
	<dt> <strong>Localization</strong></dt>
	<dd><p>This directory organizes translation messages specifically produced to
	satisfy internationalization needs inside the CentOS Artwork
	Repository. This place is perfect to consolidate <em>The CentOS
	Translation SIG</em>. If you love translating, you'll find lot of messages
	waiting for you to translate here.
	</p>
	<p>See section <a href="repository_51.html#SEC258">The <tt>`trunk/Locales'</tt> Directory</a>, for more information.
	</p>
	</dd>
	<dt> <strong>Automation</strong></dt>
	<dd><p>This directory organizes the production of <code>centos-art</code>, a
	command-line interface specially designed to automate most frequent
	tasks in the repository (e.g., image rendition, documenting directory
	structures, translating content, etc.). If you can't resist the idea
	of automating repeatable tasks, then take a look here.
	</p>
	<p>See section <a href="repository_64.html#SEC323">The <tt>`trunk/Scripts'</tt> Directory</a>, for more information.
	</p></dd>
	</dl>


	<a name="SEC20"></a>
	<h3 class="subsection"> 2.3.3 Usage </h3>

	<p>When we need to create branches or tags, the <tt>`trunk/'</tt> directory
	structure is the one used as reference to build them. Take a look at
	the following directory structure construction and notice how the
	<tt>`/Scripts/Bash/Cli'</tt> string is repeated in the paths and how it is
	put on it:
	</p>
	<dl compact="compact">
	<dt> <tt>`trunk/Scripts/Bash/Cli'</tt></dt>
	<dd>
	<p>This directory structure provides the main development line of the
	<tt>`centos-art'</tt> command-line interface written in bash. In this
	directory changes may occur pretty fast and in unpredicted ways. This
	configuration could provoke that the <tt>`centos-art'</tt> command-line
	stop working in a manner unprediceted due the way changes are
	introduced to it.
	</p>
	</dd>
	<dt> <tt>`branches/Scripts/Bash/Cli/1'</tt></dt>
	<dd>
	<p>This directory structure, however, provides an intermediate place for
	less unpredicted changes and that way to provide more stability than
	<tt>`trunk/'</tt> directory structure is able to provide.
	</p>
	<p>Notice that we used a number to identify the branch (the number `1' in
	this case). Changing this number we could create several branches
	that could be maintained at the same time to fix specific problems
	simultaneausly otherwise difficult to fix in an unpredictable area
	like that provided by <tt>`trunk/'</tt> directory structure. Once the
	specific problems has been fixed, the branch is merged into
	<tt>`trunk/'</tt> and removed from the repository file system.
	</p>
	<p>If you are the only person working in the repository, you probably
	don't want to worry about creating branches at all and prefer going
	straight from trunk to tags. Ask yourself: If I'm the only person
	working in the trunk directory structure whom else could introduce
	unpredictable changes but myself? In that case, such changes wouldn't
	be unpredictable at all, don't you think?
	</p>
	</dd>
	<dt> <tt>`tags/Scripts/Bash/Cli/1.0'</tt></dt>
	<dd>
	<p>Instead of removing the branch directory structure from the repository
	file system, it could be very convenient to create a check-point in
	time with such problems fixed and so providing a predictable release
	of the <tt>`centos-art'</tt> command-line interface.
	</p>
	<p>Notice that we used the number 1.0 to store the tag. These means that
	we are creating the tag number 0 from the branch numbered as 1 (i.e.,
	the first number before the dot represents the branch number and the
	second number after the dot represents the tag number).
	</p>
	<p>Using the <tt>`centos-art'</tt> command-line from tags diectory structure
	does provide more stable results than those from branches or trunk
	directory structures. The tags directory structure doesn't introduce
	changes at all, so you are safe to get what you expect after reading
	the release notes for that tag. This configuration is not possible
	supported on trunk nor branches since they do change through time.
	</p></dd>
	</dl>

	<p>It seems to be no other immediate use for this directory but those
	described above.
	</p>

	<a name="SEC21"></a>
	<h3 class="subsection"> 2.3.4 See also </h3>

	<table class="menu" border="0" cellspacing="0">
	<tr><td align="left" valign="top"><a href="repository_5.html#SEC5">2.1 The <tt>`branches'</tt> Directory</a></td><td>  </td><td align="left" valign="top">
	</td></tr>
	<tr><td align="left" valign="top"><a href="repository_6.html#SEC12">2.2 The <tt>`tags'</tt> Directory</a></td><td>  </td><td align="left" valign="top">
	</td></tr>
	</table>



	<table cellpadding="1" cellspacing="1" border="0">
	<tr><td valign="middle" align="left">[<a href="#SEC20" title="Previous section in reading order"> < </a>]</td>
	<td valign="middle" align="left">[<a href="repository_8.html#SEC22" title="Next section in reading order"> > </a>]</td>
	<td valign="middle" align="left">   </td>
	<td valign="middle" align="left">[<a href="repository_4.html#SEC4" title="Beginning of this chapter or previous chapter"> << </a>]</td>
	<td valign="middle" align="left">[<a href="#SEC17" title="Up section"> Up </a>]</td>
	<td valign="middle" align="left">[<a href="repository_79.html#SEC416" title="Next chapter"> >> </a>]</td>
	</tr></table>
	<p>
	<font size="-1">
	This document was generated on <i>March, 8 2011</i> using <a class="www" href="http://texi2html.cvshome.org/"><i>texi2html 1.76</i></a>.
	</font>
	<br>

	</p>
	</body>
	</html>

centos / artwork-archive

Source Code

Files