[gentoo-commits] proj/R_overlay:master commit in: doc/html/

["André Erdmann" <dywi@mailerd.de>]

commit:     6d38ed2962e1fa1cd42217c55edb6b5d138c0384
Author:     André Erdmann <dywi <AT> mailerd <DOT> de>
AuthorDate: Fri Aug 10 17:56:23 2012 +0000
Commit:     André Erdmann <dywi <AT> mailerd <DOT> de>
CommitDate: Fri Aug 10 17:56:23 2012 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/R_overlay.git;a=commit;h=6d38ed29

usage guide, html: numbered sections

---
 doc/html/usage.html |  130 +++++++++++++++++++++++++-------------------------
 1 files changed, 65 insertions(+), 65 deletions(-)

diff --git a/doc/html/usage.html b/doc/html/usage.html
index 8027b22..37e3c27 100644
--- a/doc/html/usage.html
+++ b/doc/html/usage.html
@@ -319,68 +319,68 @@ ul.auto-toc {
 
 <div class="contents topic" id="contents">
 <p class="topic-title first">Contents</p>
-<ul class="simple">
-<li><a class="reference internal" href="#introduction" id="id1">Introduction</a></li>
-<li><a class="reference internal" href="#installation" id="id2">Installation</a><ul>
-<li><a class="reference internal" href="#prerequisites" id="id3">Prerequisites</a></li>
-<li><a class="reference internal" href="#via-emerge-gentoo" id="id4">via emerge (Gentoo)</a></li>
-<li><a class="reference internal" href="#manual-installation" id="id5">Manual Installation</a></li>
-<li><a class="reference internal" href="#using-roverlay-without-installation" id="id6">Using <em>roverlay</em> without installation</a></li>
+<ul class="auto-toc simple">
+<li><a class="reference internal" href="#introduction" id="id1">1&nbsp;&nbsp;&nbsp;Introduction</a></li>
+<li><a class="reference internal" href="#installation" id="id2">2&nbsp;&nbsp;&nbsp;Installation</a><ul class="auto-toc">
+<li><a class="reference internal" href="#prerequisites" id="id3">2.1&nbsp;&nbsp;&nbsp;Prerequisites</a></li>
+<li><a class="reference internal" href="#via-emerge-gentoo" id="id4">2.2&nbsp;&nbsp;&nbsp;via emerge (Gentoo)</a></li>
+<li><a class="reference internal" href="#manual-installation" id="id5">2.3&nbsp;&nbsp;&nbsp;Manual Installation</a></li>
+<li><a class="reference internal" href="#using-roverlay-without-installation" id="id6">2.4&nbsp;&nbsp;&nbsp;Using <em>roverlay</em> without installation</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#running-roverlay" id="id7">Running Roverlay</a><ul>
-<li><a class="reference internal" href="#required-configuration-steps" id="id8">Required configuration steps</a></li>
-<li><a class="reference internal" href="#running-it" id="id9">Running it</a></li>
-<li><a class="reference internal" href="#providing-a-package-mirror" id="id10">Providing a package mirror</a></li>
+<li><a class="reference internal" href="#running-roverlay" id="id7">3&nbsp;&nbsp;&nbsp;Running Roverlay</a><ul class="auto-toc">
+<li><a class="reference internal" href="#required-configuration-steps" id="id8">3.1&nbsp;&nbsp;&nbsp;Required configuration steps</a></li>
+<li><a class="reference internal" href="#running-it" id="id9">3.2&nbsp;&nbsp;&nbsp;Running it</a></li>
+<li><a class="reference internal" href="#providing-a-package-mirror" id="id10">3.3&nbsp;&nbsp;&nbsp;Providing a package mirror</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#implementation-overview" id="id11">Implementation Overview</a><ul>
-<li><a class="reference internal" href="#repositories-getting-packages" id="id12">Repositories / Getting Packages</a><ul>
-<li><a class="reference internal" href="#a-word-about-repo-config-files" id="id13">A word about repo config files</a></li>
-<li><a class="reference internal" href="#rsync-repos" id="id14">Rsync repos</a></li>
-<li><a class="reference internal" href="#getting-packages-from-a-repository-that-supports-http-only" id="id15">Getting packages from a repository that supports http only</a></li>
-<li><a class="reference internal" href="#getting-packages-from-several-remotes-using-http-and-a-package-list" id="id16">Getting packages from several remotes using http and a package list</a></li>
-<li><a class="reference internal" href="#using-local-directories" id="id17">Using local directories</a></li>
+<li><a class="reference internal" href="#implementation-overview" id="id11">4&nbsp;&nbsp;&nbsp;Implementation Overview</a><ul class="auto-toc">
+<li><a class="reference internal" href="#repositories-getting-packages" id="id12">4.1&nbsp;&nbsp;&nbsp;Repositories / Getting Packages</a><ul class="auto-toc">
+<li><a class="reference internal" href="#a-word-about-repo-config-files" id="id13">4.1.1&nbsp;&nbsp;&nbsp;A word about repo config files</a></li>
+<li><a class="reference internal" href="#rsync-repos" id="id14">4.1.2&nbsp;&nbsp;&nbsp;Rsync repos</a></li>
+<li><a class="reference internal" href="#getting-packages-from-a-repository-that-supports-http-only" id="id15">4.1.3&nbsp;&nbsp;&nbsp;Getting packages from a repository that supports http only</a></li>
+<li><a class="reference internal" href="#getting-packages-from-several-remotes-using-http-and-a-package-list" id="id16">4.1.4&nbsp;&nbsp;&nbsp;Getting packages from several remotes using http and a package list</a></li>
+<li><a class="reference internal" href="#using-local-directories" id="id17">4.1.5&nbsp;&nbsp;&nbsp;Using local directories</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#dependency-rules-resolving-dependencies" id="id18">Dependency Rules / Resolving Dependencies</a><ul>
-<li><a class="reference internal" href="#dependency-types" id="id19">Dependency types</a></li>
-<li><a class="reference internal" href="#simple-dependency-rules" id="id20">Simple Dependency Rules</a><ul>
-<li><a class="reference internal" href="#rule-variants" id="id21">Rule Variants</a></li>
-<li><a class="reference internal" href="#rule-types" id="id22">Rule types</a></li>
-<li><a class="reference internal" href="#rule-file-examples" id="id23">Rule File Examples</a></li>
-<li><a class="reference internal" href="#rule-file-syntax" id="id24">Rule File Syntax</a></li>
+<li><a class="reference internal" href="#dependency-rules-resolving-dependencies" id="id18">4.2&nbsp;&nbsp;&nbsp;Dependency Rules / Resolving Dependencies</a><ul class="auto-toc">
+<li><a class="reference internal" href="#dependency-types" id="id19">4.2.1&nbsp;&nbsp;&nbsp;Dependency types</a></li>
+<li><a class="reference internal" href="#simple-dependency-rules" id="id20">4.2.2&nbsp;&nbsp;&nbsp;Simple Dependency Rules</a><ul class="auto-toc">
+<li><a class="reference internal" href="#rule-variants" id="id21">4.2.2.1&nbsp;&nbsp;&nbsp;Rule Variants</a></li>
+<li><a class="reference internal" href="#rule-types" id="id22">4.2.2.2&nbsp;&nbsp;&nbsp;Rule types</a></li>
+<li><a class="reference internal" href="#rule-file-examples" id="id23">4.2.2.3&nbsp;&nbsp;&nbsp;Rule File Examples</a></li>
+<li><a class="reference internal" href="#rule-file-syntax" id="id24">4.2.2.4&nbsp;&nbsp;&nbsp;Rule File Syntax</a></li>
 </ul>
 </li>
 </ul>
 </li>
-<li><a class="reference internal" href="#expected-overlay-result-structure-of-the-generated-overlay" id="id25">Expected Overlay Result / Structure of the generated overlay</a></li>
+<li><a class="reference internal" href="#expected-overlay-result-structure-of-the-generated-overlay" id="id25">4.3&nbsp;&nbsp;&nbsp;Expected Overlay Result / Structure of the generated overlay</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#configuration-reference" id="id26">Configuration Reference</a><ul>
-<li><a class="reference internal" href="#dependency-rules" id="id27">Dependency Rules</a></li>
-<li><a class="reference internal" href="#repositories" id="id28">Repositories</a></li>
-<li><a class="reference internal" href="#main-config" id="id29">Main Config</a></li>
-<li><a class="reference internal" href="#field-definition" id="id30">Field Definition</a></li>
+<li><a class="reference internal" href="#configuration-reference" id="id26">5&nbsp;&nbsp;&nbsp;Configuration Reference</a><ul class="auto-toc">
+<li><a class="reference internal" href="#dependency-rules" id="id27">5.1&nbsp;&nbsp;&nbsp;Dependency Rules</a></li>
+<li><a class="reference internal" href="#repositories" id="id28">5.2&nbsp;&nbsp;&nbsp;Repositories</a></li>
+<li><a class="reference internal" href="#main-config" id="id29">5.3&nbsp;&nbsp;&nbsp;Main Config</a></li>
+<li><a class="reference internal" href="#field-definition" id="id30">5.4&nbsp;&nbsp;&nbsp;Field Definition</a></li>
 </ul>
 </li>
-<li><a class="reference internal" href="#appendix" id="id31">Appendix</a><ul>
-<li><a class="reference internal" href="#default-field-definition-file" id="id32">Default Field Definition File</a></li>
+<li><a class="reference internal" href="#appendix" id="id31">6&nbsp;&nbsp;&nbsp;Appendix</a><ul class="auto-toc">
+<li><a class="reference internal" href="#default-field-definition-file" id="id32">6.1&nbsp;&nbsp;&nbsp;Default Field Definition File</a></li>
 </ul>
 </li>
 </ul>
 </div>
 <div class="section" id="introduction">
-<h1><a class="toc-backref" href="#id1">Introduction</a></h1>
+<h1><a class="toc-backref" href="#id1">1&nbsp;&nbsp;&nbsp;Introduction</a></h1>
 <p><em>roverlay</em> is
 Automatically Generated Overlay of R packages;;
 GSoC Project;;
 &lt;&gt;;;</p>
 </div>
 <div class="section" id="installation">
-<h1><a class="toc-backref" href="#id2">Installation</a></h1>
+<h1><a class="toc-backref" href="#id2">2&nbsp;&nbsp;&nbsp;Installation</a></h1>
 <div class="section" id="prerequisites">
-<h2><a class="toc-backref" href="#id3">Prerequisites</a></h2>
+<h2><a class="toc-backref" href="#id3">2.1&nbsp;&nbsp;&nbsp;Prerequisites</a></h2>
 <ul>
 <li><p class="first">python &gt;= 2.7 (tested with python 2.7 and 3.2)</p>
 </li>
@@ -425,13 +425,13 @@ writing to a tmpfs, most time is spent for Manifest creation&gt;</p>
 </ul>
 </div>
 <div class="section" id="via-emerge-gentoo">
-<h2><a class="toc-backref" href="#id4">via emerge (Gentoo)</a></h2>
+<h2><a class="toc-backref" href="#id4">2.2&nbsp;&nbsp;&nbsp;via emerge (Gentoo)</a></h2>
 <p>A live ebuild is available, <a class="reference external" href="http://git.overlays.gentoo.org/gitweb/?p=proj/R_overlay.git;a=blob;f=roverlay-9999.ebuild;hb=refs/heads/master">roverlay-9999.ebuild</a>.
 Add it to your local overlay and run <tt class="docutils literal">emerge roverlay</tt>, which will also
 install all config files into <em>/etc/roverlay</em>.</p>
 </div>
 <div class="section" id="manual-installation">
-<h2><a class="toc-backref" href="#id5">Manual Installation</a></h2>
+<h2><a class="toc-backref" href="#id5">2.3&nbsp;&nbsp;&nbsp;Manual Installation</a></h2>
 <p>After installing the dependencies as listed in <a class="reference internal" href="#prerequisites">Prerequisites</a>,
 clone the <a class="reference external" href="http://git.overlays.gentoo.org/gitweb/?p=proj/R_overlay.git;a=summary">roverlay git repo</a> and then
 install <em>roverlay</em> and its python modules:</p>
@@ -465,7 +465,7 @@ any config files!</p>
 </div>
 </div>
 <div class="section" id="using-roverlay-without-installation">
-<h2><a class="toc-backref" href="#id6">Using <em>roverlay</em> without installation</a></h2>
+<h2><a class="toc-backref" href="#id6">2.4&nbsp;&nbsp;&nbsp;Using <em>roverlay</em> without installation</a></h2>
 <p>This is possible, too. Make sure to meet the dependencies as listed
 in <a class="reference internal" href="#prerequisites">Prerequisites</a>.
 Then, simply clone the git repository to a local directory that
@@ -485,9 +485,9 @@ will later be referenced as the <em>R Overlay src directory</em>.</p>
 </div>
 </div>
 <div class="section" id="running-roverlay">
-<h1><a class="toc-backref" href="#id7">Running Roverlay</a></h1>
+<h1><a class="toc-backref" href="#id7">3&nbsp;&nbsp;&nbsp;Running Roverlay</a></h1>
 <div class="section" id="required-configuration-steps">
-<h2><a class="toc-backref" href="#id8">Required configuration steps</a></h2>
+<h2><a class="toc-backref" href="#id8">3.1&nbsp;&nbsp;&nbsp;Required configuration steps</a></h2>
 <p><em>roverlay</em> needs a configuration file to run.</p>
 <p>If you've installed <em>roverlay</em> with <em>emerge</em>, it will look for the config
 file in that order:</p>
@@ -584,7 +584,7 @@ named <em>R-packages.eclass</em> should be part of your installation.</p>
 <p>For details and a full configuration reference, see <a class="reference internal" href="#configuration-reference">Configuration Reference</a>.</p>
 </div>
 <div class="section" id="running-it">
-<h2><a class="toc-backref" href="#id9">Running it</a></h2>
+<h2><a class="toc-backref" href="#id9">3.2&nbsp;&nbsp;&nbsp;Running it</a></h2>
 <p>If you've installed <em>roverlay</em>, you can run it with <tt class="docutils literal">roverlay</tt>, otherwise
 you'll have to cd into the <em>R overlay src directory</em> and run <tt class="docutils literal">./roverlay.py</tt>.</p>
 <p>In any case, the basic <em>roverlay</em> script usage is</p>
@@ -695,7 +695,7 @@ and resolving dependencies.</p>
 </dl>
 </div>
 <div class="section" id="providing-a-package-mirror">
-<h2><a class="toc-backref" href="#id10">Providing a package mirror</a></h2>
+<h2><a class="toc-backref" href="#id10">3.3&nbsp;&nbsp;&nbsp;Providing a package mirror</a></h2>
 <p>&lt;No recommendations at this time. The current ManifestCreation implementation
 creates a directory <em>&lt;distfiles root&gt;/__tmp__</em> with symlinks to all packages,
 which could be used for providing packages, but this may change
@@ -704,7 +704,7 @@ in near future since external Manifest creation is too slow
 </div>
 </div>
 <div class="section" id="implementation-overview">
-<h1><a class="toc-backref" href="#id11">Implementation Overview</a></h1>
+<h1><a class="toc-backref" href="#id11">4&nbsp;&nbsp;&nbsp;Implementation Overview</a></h1>
 <p>This section gives a basic overview of how <em>roverlay</em> works.</p>
 <p>&lt;how <em>roverlay</em> basically works:&gt;</p>
 <ol class="arabic simple">
@@ -757,13 +757,13 @@ and may decide to write <em>p</em>'s ebuild now (or later)</li>
 </li>
 </ol>
 <div class="section" id="repositories-getting-packages">
-<h2><a class="toc-backref" href="#id12">Repositories / Getting Packages</a></h2>
+<h2><a class="toc-backref" href="#id12">4.1&nbsp;&nbsp;&nbsp;Repositories / Getting Packages</a></h2>
 <p><em>roverlay</em> is capable of downloading R packages via rsync and http,
 and is able to use any packages locally available. The concrete method used
 to get and use the packages is determined by the concrete
 <strong>type of a repository</strong> and that's what this section is about.</p>
 <div class="section" id="a-word-about-repo-config-files">
-<h3><a class="toc-backref" href="#id13">A word about repo config files</a></h3>
+<h3><a class="toc-backref" href="#id13">4.1.1&nbsp;&nbsp;&nbsp;A word about repo config files</a></h3>
 <p>Repo config files use <a class="reference external" href="http://docs.python.org/library/configparser.html">ConfigParser</a> syntax (known from ini files).</p>
 <p>Each repo entry section is introduced with <tt class="docutils literal">[&lt;repo name&gt;]</tt> and defines</p>
 <ul class="simple">
@@ -801,7 +801,7 @@ creating the default directory.</p>
 </div>
 </div>
 <div class="section" id="rsync-repos">
-<span id="rsync"></span><h3><a class="toc-backref" href="#id14">Rsync repos</a></h3>
+<span id="rsync"></span><h3><a class="toc-backref" href="#id14">4.1.2&nbsp;&nbsp;&nbsp;Rsync repos</a></h3>
 <p>Runs <em>rsync</em> to download packages. Automatic sync retries are supported if
 <em>rsync</em>'s exit codes indicates chances of success.
 For example, up to 3 retries are granted if <em>rsync</em> returns
@@ -844,7 +844,7 @@ Options with whitespace are not supported.</li>
 </ul>
 </div>
 <div class="section" id="getting-packages-from-a-repository-that-supports-http-only">
-<span id="websync-repo"></span><h3><a class="toc-backref" href="#id15">Getting packages from a repository that supports http only</a></h3>
+<span id="websync-repo"></span><h3><a class="toc-backref" href="#id15">4.1.3&nbsp;&nbsp;&nbsp;Getting packages from a repository that supports http only</a></h3>
 <p>This is your best bet if the remote is a repository but doesn't offer
 rsync access. Basic digest verification is supported (MD5).
 The remote has to have a package list file, typically named
@@ -894,7 +894,7 @@ Defaults to <em>src_uri</em>/<em>pkglist_file</em></li>
 </div>
 </div>
 <div class="section" id="getting-packages-from-several-remotes-using-http-and-a-package-list">
-<span id="websync-pkglist"></span><h3><a class="toc-backref" href="#id16">Getting packages from several remotes using http and a package list</a></h3>
+<span id="websync-pkglist"></span><h3><a class="toc-backref" href="#id16">4.1.4&nbsp;&nbsp;&nbsp;Getting packages from several remotes using http and a package list</a></h3>
 <p>This is not a real repository type, instead it creates a <em>local</em> repository
 by downloading single R packages from different remotes.
 Its only requirement is that a package is downloadable via http.
@@ -921,7 +921,7 @@ file would be:</p>
 </ul>
 </div>
 <div class="section" id="using-local-directories">
-<span id="local"></span><h3><a class="toc-backref" href="#id17">Using local directories</a></h3>
+<span id="local"></span><h3><a class="toc-backref" href="#id17">4.1.5&nbsp;&nbsp;&nbsp;Using local directories</a></h3>
 <p>Using local package directories is possible, too.</p>
 <p>Example:</p>
 <pre class="code ini literal-block">
@@ -944,9 +944,9 @@ you should consider using one of the <strong>websync</strong> repo types,
 </div>
 </div>
 <div class="section" id="dependency-rules-resolving-dependencies">
-<h2><a class="toc-backref" href="#id18">Dependency Rules / Resolving Dependencies</a></h2>
+<h2><a class="toc-backref" href="#id18">4.2&nbsp;&nbsp;&nbsp;Dependency Rules / Resolving Dependencies</a></h2>
 <div class="section" id="dependency-types">
-<h3><a class="toc-backref" href="#id19">Dependency types</a></h3>
+<h3><a class="toc-backref" href="#id19">4.2.1&nbsp;&nbsp;&nbsp;Dependency types</a></h3>
 <p>Every <em>dependency string</em> has a <em>dependency type</em> that declares how a
 dependency should be resolved. It has one or more of these properties:</p>
 <dl class="docutils">
@@ -974,7 +974,7 @@ gets the <em>&quot;package dependency and optional&quot;</em> type,
 whereas the <em>SystemRequirements</em> gets <em>&quot;system dependency and mandatory&quot;</em>.</p>
 </div>
 <div class="section" id="simple-dependency-rules">
-<h3><a class="toc-backref" href="#id20">Simple Dependency Rules</a></h3>
+<h3><a class="toc-backref" href="#id20">4.2.2&nbsp;&nbsp;&nbsp;Simple Dependency Rules</a></h3>
 <p><em>Simple dependency rules</em> use a dictionary and string transformations
 to resolve dependencies. <em>Fuzzy simple dependency rules</em> extend these by
 a set of regexes, which allows to resolve many dependency strings that
@@ -983,7 +983,7 @@ minimally differ (e.g. only in the required version and/or comments:
 dictionary entry.</p>
 <p>This is the only rule implementation currently available.</p>
 <div class="section" id="rule-variants">
-<h4><a class="toc-backref" href="#id21">Rule Variants</a></h4>
+<h4><a class="toc-backref" href="#id21">4.2.2.1&nbsp;&nbsp;&nbsp;Rule Variants</a></h4>
 <dl class="docutils">
 <dt>default</dt>
 <dd>The expected behavior of a dictionary-based rule: It matches one or more
@@ -994,7 +994,7 @@ resolve them as <strong>nothing</strong>.</dd>
 </dl>
 </div>
 <div class="section" id="rule-types">
-<h4><a class="toc-backref" href="#id22">Rule types</a></h4>
+<h4><a class="toc-backref" href="#id22">4.2.2.2&nbsp;&nbsp;&nbsp;Rule types</a></h4>
 <dl class="docutils">
 <dt>Simple Rules</dt>
 <dd><p class="first">A simple rule resolves <strong>exact string matches</strong> (case-insensitive).</p>
@@ -1035,7 +1035,7 @@ as &quot;&lt;dev-lang/R-2.14&quot;</li>
 </dl>
 </div>
 <div class="section" id="rule-file-examples">
-<h4><a class="toc-backref" href="#id23">Rule File Examples</a></h4>
+<h4><a class="toc-backref" href="#id23">4.2.2.3&nbsp;&nbsp;&nbsp;Rule File Examples</a></h4>
 <p>This sections lists some rule file examples.
 See <a class="reference internal" href="#rule-file-syntax">Rule File Syntax</a> for a formal&lt;precise,..?&gt; description.</p>
 <dl class="docutils">
@@ -1087,7 +1087,7 @@ if you've installed <em>roverlay</em> with <em>emerge</em>,
 else in <em>&lt;R Overlay src directory&gt;/simple-deprules.d</em>.</p>
 </div>
 <div class="section" id="rule-file-syntax">
-<h4><a class="toc-backref" href="#id24">Rule File Syntax</a></h4>
+<h4><a class="toc-backref" href="#id24">4.2.2.4&nbsp;&nbsp;&nbsp;Rule File Syntax</a></h4>
 <p>Simple dependency rule files have a special syntax. Each rule is introduced
 with the resolving <em>dependency</em> prefixed by a <em>keychar</em> that sets the rule
 type if required. The <em>dependency strings</em> resolved by this rule are listed
@@ -1190,7 +1190,7 @@ will be read as normal <em>dependency strings</em>.</dd>
 </div>
 </div>
 <div class="section" id="expected-overlay-result-structure-of-the-generated-overlay">
-<h2><a class="toc-backref" href="#id25">Expected Overlay Result / Structure of the generated overlay</a></h2>
+<h2><a class="toc-backref" href="#id25">4.3&nbsp;&nbsp;&nbsp;Expected Overlay Result / Structure of the generated overlay</a></h2>
 <p>Assuming that you're using the default configuration (where possible) and
 the <em>R-packages</em> eclass file, the result should look like:</p>
 <pre class="code text literal-block">
@@ -1211,17 +1211,17 @@ the <em>R-packages</em> eclass file, the result should look like:</p>
 </div>
 </div>
 <div class="section" id="configuration-reference">
-<h1><a class="toc-backref" href="#id26">Configuration Reference</a></h1>
+<h1><a class="toc-backref" href="#id26">5&nbsp;&nbsp;&nbsp;Configuration Reference</a></h1>
 <div class="section" id="dependency-rules">
-<h2><a class="toc-backref" href="#id27">Dependency Rules</a></h2>
+<h2><a class="toc-backref" href="#id27">5.1&nbsp;&nbsp;&nbsp;Dependency Rules</a></h2>
 <p>&lt;merge with basic..overview::deprules&gt;</p>
 </div>
 <div class="section" id="repositories">
-<h2><a class="toc-backref" href="#id28">Repositories</a></h2>
+<h2><a class="toc-backref" href="#id28">5.2&nbsp;&nbsp;&nbsp;Repositories</a></h2>
 <p>&lt;merge with basic..overview::repo&gt;</p>
 </div>
 <div class="section" id="main-config">
-<h2><a class="toc-backref" href="#id29">Main Config</a></h2>
+<h2><a class="toc-backref" href="#id29">5.3&nbsp;&nbsp;&nbsp;Main Config</a></h2>
 <dl class="docutils" id="distfiles-root">
 <dt>DISTFILES_ROOT</dt>
 <dd>&lt;&gt;</dd>
@@ -1229,7 +1229,7 @@ the <em>R-packages</em> eclass file, the result should look like:</p>
 <p>The main config file uses shell syntax.</p>
 </div>
 <div class="section" id="field-definition">
-<h2><a class="toc-backref" href="#id30">Field Definition</a></h2>
+<h2><a class="toc-backref" href="#id30">5.4&nbsp;&nbsp;&nbsp;Field Definition</a></h2>
 <p>The field definition file uses <a class="reference external" href="http://docs.python.org/library/configparser.html">ConfigParser</a> syntax. For an example, see
 <a class="reference internal" href="#default-field-definition-file">default field definition file</a>.</p>
 <p>Each information field has its own section which declares a set of options
@@ -1310,9 +1310,9 @@ are ignored, too, the main difference is the log message.</dd>
 </div>
 </div>
 <div class="section" id="appendix">
-<h1><a class="toc-backref" href="#id31">Appendix</a></h1>
+<h1><a class="toc-backref" href="#id31">6&nbsp;&nbsp;&nbsp;Appendix</a></h1>
 <div class="section" id="default-field-definition-file">
-<h2><a class="toc-backref" href="#id32">Default Field Definition File</a></h2>
+<h2><a class="toc-backref" href="#id32">6.1&nbsp;&nbsp;&nbsp;Default Field Definition File</a></h2>
 <p>This is the default field definition file (without any ignored fields):</p>
 <pre class="code ini literal-block">
 <span class="k">[Description]</span>