diff options
author | 2024-03-23 18:23:37 +0100 | |
---|---|---|
committer | 2024-03-23 18:23:37 +0100 | |
commit | a5c213d53976e7b9ef0a5206a5f4f6fc4128f1c4 (patch) | |
tree | 24c7543d84b60c984801009330d661ce61903cd8 /combined.html | |
parent | Rebuild (diff) | |
download | policy-guide-a5c213d53976e7b9ef0a5206a5f4f6fc4128f1c4.tar.gz policy-guide-a5c213d53976e7b9ef0a5206a5f4f6fc4128f1c4.tar.bz2 policy-guide-a5c213d53976e7b9ef0a5206a5f4f6fc4128f1c4.zip |
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'combined.html')
-rw-r--r-- | combined.html | 206 |
1 files changed, 102 insertions, 104 deletions
diff --git a/combined.html b/combined.html index 4412881..adabc6d 100644 --- a/combined.html +++ b/combined.html @@ -5,20 +5,21 @@ <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> - <meta name="viewport" content="width=device-width, initial-scale=1"><meta name="generator" content="Docutils 0.19: https://docutils.sourceforge.io/" /> + <meta name="viewport" content="width=device-width, initial-scale=1"><meta name="viewport" content="width=device-width, initial-scale=1" /> <title>Gentoo Policy Guide documentation</title> - <link rel="stylesheet" href="_static/tyrian-sphinx-theme.css" type="text/css" /> - <link rel="stylesheet" href="_static/pygments.css" type="text/css" /> - <link rel="stylesheet" href="_static/custom.css" type="text/css" /> + <link rel="stylesheet" type="text/css" href="_static/pygments.css" /> + <link rel="stylesheet" type="text/css" href="_static/tyrian-sphinx-theme.css" /> + <link rel="stylesheet" type="text/css" href="_static/custom.css" /> <link rel="icon" href="https://www.gentoo.org/favicon.ico" type="image/x-icon"> <link href="https://assets.gentoo.org/tyrian/bootstrap.min.css" rel="stylesheet" media="screen"> <link href="https://assets.gentoo.org/tyrian/tyrian.min.css" rel="stylesheet" media="screen"> <link rel="stylesheet" type="text/css" href="_static/pygments.css" /> <link rel="stylesheet" type="text/css" href="_static/tyrian-sphinx-theme.css" /> + <link rel="stylesheet" type="text/css" href="_static/custom.css" /> <script type="text/javascript" id="documentation_options" data-url_root="./" src="_static/documentation_options.js"></script> - <script data-url_root="./" id="documentation_options" src="_static/documentation_options.js"></script> + <script src="_static/documentation_options.js"></script> <script src="_static/doctools.js"></script> <script src="_static/sphinx_highlight.js"></script> <link rel="index" title="Index" href="genindex.html" /> @@ -110,7 +111,7 @@ <section id="gentoo-policy-guide"> -<h1>Gentoo Policy Guide<a class="headerlink" href="#gentoo-policy-guide" title="Permalink to this heading">¶</a></h1> +<h1>Gentoo Policy Guide<a class="headerlink" href="#gentoo-policy-guide" title="Link to this heading">¶</a></h1> <p>Gentoo Policy Guide aims to become a definitive clear source of all Tree Policies that are currently binding to Gentoo developers. It combines both policies that are global by design (i.e. set by the QA @@ -120,9 +121,9 @@ indication of the body setting the policy, and therefore the process in which the policy can be updated.</p> <div class="toctree-wrapper compound"> <span id="document-preface"></span><section id="preface"> -<h2>Preface<a class="headerlink" href="#preface" title="Permalink to this heading">¶</a></h2> +<h2>Preface<a class="headerlink" href="#preface" title="Link to this heading">¶</a></h2> <section id="introduction"> -<h3>Introduction<a class="headerlink" href="#introduction" title="Permalink to this heading">¶</a></h3> +<h3>Introduction<a class="headerlink" href="#introduction" title="Link to this heading">¶</a></h3> <p>Gentoo Policy Guide aims to become a definitive clear source of all Tree Policies that are currently binding to Gentoo developers. It combines both policies that are global by design (i.e. set by the QA @@ -132,7 +133,7 @@ indication of the body setting the policy, and therefore the process in which the policy can be updated.</p> </section> <section id="authors"> -<h3>Authors<a class="headerlink" href="#authors" title="Permalink to this heading">¶</a></h3> +<h3>Authors<a class="headerlink" href="#authors" title="Link to this heading">¶</a></h3> <p>This document is maintained by the Gentoo <a class="reference external" href="https://wiki.gentoo.org/wiki/Project:Quality_Assurance">QA project</a>.</p> <p>The current text authors are:</p> <ul class="simple"> @@ -141,15 +142,15 @@ in which the policy can be updated.</p> </ul> </section> <section id="license"> -<h3>License<a class="headerlink" href="#license" title="Permalink to this heading">¶</a></h3> +<h3>License<a class="headerlink" href="#license" title="Link to this heading">¶</a></h3> <p>This work is licensed under the <a class="reference external" href="https://creativecommons.org/licenses/by-sa/4.0/.">Creative Commons Attribution-ShareAlike 4.0 International License</a>.</p> </section> </section> <span id="document-motivation"></span><section id="motivation-and-history"> -<h2>Motivation and history<a class="headerlink" href="#motivation-and-history" title="Permalink to this heading">¶</a></h2> +<h2>Motivation and history<a class="headerlink" href="#motivation-and-history" title="Link to this heading">¶</a></h2> <section id="historical-state-of-policy-documentation"> -<h3>Historical state of policy documentation<a class="headerlink" href="#historical-state-of-policy-documentation" title="Permalink to this heading">¶</a></h3> +<h3>Historical state of policy documentation<a class="headerlink" href="#historical-state-of-policy-documentation" title="Link to this heading">¶</a></h3> <p>At the time, Gentoo was lacking a clear and focused document listing all development-related policies in a concise and clear way.</p> <p><a class="reference external" href="https://projects.gentoo.org/pms/latest/pms.html">PMS</a> provided a technical specification for the ebuild files but did @@ -176,7 +177,7 @@ established less or more formally in the past but were never really written down.</p> </section> <section id="purpose-of-the-policy-guide"> -<h3>Purpose of the Policy Guide<a class="headerlink" href="#purpose-of-the-policy-guide" title="Permalink to this heading">¶</a></h3> +<h3>Purpose of the Policy Guide<a class="headerlink" href="#purpose-of-the-policy-guide" title="Link to this heading">¶</a></h3> <p>The Policy Guide was created in order to address aforementioned documentation deficiencies. Its primary purpose is to collect all applicable policies from various sources and combine them into a single @@ -193,9 +194,9 @@ devmanual) should conform to policies stated here.</p> </section> </section> <span id="document-basics"></span><section id="basic-information"> -<h2>Basic information<a class="headerlink" href="#basic-information" title="Permalink to this heading">¶</a></h2> +<h2>Basic information<a class="headerlink" href="#basic-information" title="Link to this heading">¶</a></h2> <section id="goals-of-policy-making"> -<h3>Goals of policy making<a class="headerlink" href="#goals-of-policy-making" title="Permalink to this heading">¶</a></h3> +<h3>Goals of policy making<a class="headerlink" href="#goals-of-policy-making" title="Link to this heading">¶</a></h3> <p>The Gentoo policies focus on three aims:</p> <ol class="arabic simple"> <li><p><em>Portability</em>. By following the policies, it should be possible @@ -214,7 +215,7 @@ his goals and reduce the likeliness of surprising behavior.</p></li> </ol> </section> <section id="policy-compliance-checking"> -<h3>Policy compliance checking<a class="headerlink" href="#policy-compliance-checking" title="Permalink to this heading">¶</a></h3> +<h3>Policy compliance checking<a class="headerlink" href="#policy-compliance-checking" title="Link to this heading">¶</a></h3> <p>Currently, there are two kinds of tools involved in detecting policy violations:</p> <ol class="arabic simple"> @@ -237,7 +238,7 @@ supplements the direct use of linting tools by developers with reliable tree-wide scans.</p> </section> <section id="policy-enforcement"> -<h3>Policy enforcement<a class="headerlink" href="#policy-enforcement" title="Permalink to this heading">¶</a></h3> +<h3>Policy enforcement<a class="headerlink" href="#policy-enforcement" title="Link to this heading">¶</a></h3> <p>The Gentoo <a class="reference external" href="https://wiki.gentoo.org/wiki/Project:Quality_Assurance">QA team</a> is tasked with enforcement of the tree policies. Its role is governed by <a class="reference external" href="https://www.gentoo.org/glep/glep-0048.html">GLEP 48</a>. It focuses on documenting the policies, resolving doubts regarding them and educating @@ -250,7 +251,7 @@ refuses to resolve policy violations.</p> team can issue disciplinary measures against the developer in question.</p> </section> <section id="policy-making-changes-and-appeals"> -<h3>Policy making, changes and appeals<a class="headerlink" href="#policy-making-changes-and-appeals" title="Permalink to this heading">¶</a></h3> +<h3>Policy making, changes and appeals<a class="headerlink" href="#policy-making-changes-and-appeals" title="Link to this heading">¶</a></h3> <p>The majority of policies are written down and maintained by the <a class="reference external" href="https://wiki.gentoo.org/wiki/Project:Quality_Assurance">QA team</a>. Other Gentoo projects also create policies that affect their specific areas of contributions (e.g. <a class="reference external" href="https://wiki.gentoo.org/wiki/Project:Systemd">systemd project</a> created @@ -263,11 +264,11 @@ be appealed to the <a class="reference external" href="https://wiki.gentoo.org/w </section> </section> <span id="document-other-docs"></span><section id="other-policy-documents"> -<h2>Other policy documents<a class="headerlink" href="#other-policy-documents" title="Permalink to this heading">¶</a></h2> +<h2>Other policy documents<a class="headerlink" href="#other-policy-documents" title="Link to this heading">¶</a></h2> <section id="gentoo-specific-documentation"> -<h3>Gentoo-specific documentation<a class="headerlink" href="#gentoo-specific-documentation" title="Permalink to this heading">¶</a></h3> +<h3>Gentoo-specific documentation<a class="headerlink" href="#gentoo-specific-documentation" title="Link to this heading">¶</a></h3> <section id="package-manager-specification"> -<h4>Package Manager Specification<a class="headerlink" href="#package-manager-specification" title="Permalink to this heading">¶</a></h4> +<h4>Package Manager Specification<a class="headerlink" href="#package-manager-specification" title="Link to this heading">¶</a></h4> <p><a class="reference external" href="https://projects.gentoo.org/pms/latest/pms.html">PMS</a> provides the specification of ebuild format, as well as general guidelines for implementing package managers. All ebuilds in the Gentoo repository are required to conform to the PMS. Tree policies may @@ -277,7 +278,7 @@ in subsequent EAPIs that are approved by the Council. The project’s wiki page discusses how PMS can be changed via <a class="reference external" href="https://wiki.gentoo.org/wiki/Project:Package_Manager_Specification/Future_EAPI_process">future EAPI process</a>.</p> </section> <section id="gleps"> -<h4>GLEPs<a class="headerlink" href="#gleps" title="Permalink to this heading">¶</a></h4> +<h4>GLEPs<a class="headerlink" href="#gleps" title="Link to this heading">¶</a></h4> <p><a class="reference external" href="https://www.gentoo.org/glep/">GLEPs</a> provide the highest level policies applicable to Gentoo. Final or active GLEPs apply to all developers. Tree policies may impose additional restrictions on GLEPs but may not override them.</p> @@ -286,7 +287,7 @@ In general, all GLEP updates go through mailing list review and need to be approved by the Council.</p> </section> <section id="developer-manual"> -<h4>Developer Manual<a class="headerlink" href="#developer-manual" title="Permalink to this heading">¶</a></h4> +<h4>Developer Manual<a class="headerlink" href="#developer-manual" title="Link to this heading">¶</a></h4> <p><a class="reference external" href="https://devmanual.gentoo.org/">Devmanual</a> is the basic guide for ebuild developers. Besides policies, it contains many general recommendations and detailed instructions. Developer Manual does not specify policies itself, and needs to comply @@ -296,16 +297,16 @@ recommended that all changes are reviewed by the <a class="reference external" h </section> </section> <section id="external-standards"> -<h3>External standards<a class="headerlink" href="#external-standards" title="Permalink to this heading">¶</a></h3> +<h3>External standards<a class="headerlink" href="#external-standards" title="Link to this heading">¶</a></h3> <section id="posix"> -<h4>POSIX<a class="headerlink" href="#posix" title="Permalink to this heading">¶</a></h4> +<h4>POSIX<a class="headerlink" href="#posix" title="Link to this heading">¶</a></h4> <p><a class="reference external" href="http://get.posixcertified.ieee.org/">POSIX</a> is the basic standard for operating systems. However, its rules apply to the software packaged in Gentoo rather than the distribution itself. Nevertheless, when no more specific policy applies, following POSIX is recommended.</p> </section> <section id="fhs"> -<h4>FHS<a class="headerlink" href="#fhs" title="Permalink to this heading">¶</a></h4> +<h4>FHS<a class="headerlink" href="#fhs" title="Link to this heading">¶</a></h4> <p><a class="reference external" href="https://refspecs.linuxfoundation.org/fhs.shtml">FHS</a> specifies the suggested filesystem layout for Linux systems. Gentoo follows FHS only partially. Whenever Gentoo policies and FHS disagree, Gentoo policies should be followed.</p> @@ -313,9 +314,9 @@ disagree, Gentoo policies should be followed.</p> </section> </section> <span id="document-editing"></span><section id="editing-and-publishing-updates-to-this-guide"> -<h2>Editing and publishing updates to this Guide<a class="headerlink" href="#editing-and-publishing-updates-to-this-guide" title="Permalink to this heading">¶</a></h2> +<h2>Editing and publishing updates to this Guide<a class="headerlink" href="#editing-and-publishing-updates-to-this-guide" title="Link to this heading">¶</a></h2> <section id="formatting-and-style"> -<h3>Formatting and style<a class="headerlink" href="#formatting-and-style" title="Permalink to this heading">¶</a></h3> +<h3>Formatting and style<a class="headerlink" href="#formatting-and-style" title="Link to this heading">¶</a></h3> <p>While editing the Guide, please respect the existing formatting rules. Notably:</p> <ul class="simple"> @@ -330,7 +331,7 @@ rules match multiple chapters, choose the one that fits it best. Make sure to match existing keywords in index.</p> </section> <section id="getting-sources"> -<h3>Getting sources<a class="headerlink" href="#getting-sources" title="Permalink to this heading">¶</a></h3> +<h3>Getting sources<a class="headerlink" href="#getting-sources" title="Link to this heading">¶</a></h3> <p>The reference repository is hosted at git.gentoo.org, and available via <a class="reference external" href="https://gitweb.gentoo.org/proj/policy-guide.git/">proj/policy-guide.git gitweb</a>. To clone it:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="c1"># via https</span> @@ -344,7 +345,7 @@ the GitHub <a class="reference external" href="https://github.com/gentoo/policy- instead.</p> </section> <section id="building"> -<h3>Building<a class="headerlink" href="#building" title="Permalink to this heading">¶</a></h3> +<h3>Building<a class="headerlink" href="#building" title="Link to this heading">¶</a></h3> <p>A tox-file is provided to build the Guide in a virtualenv, installing all necessary dependencies. To build the HTML version, run:</p> <div class="highlight-default notranslate"><div class="highlight"><pre><span></span><span class="n">tox</span> @@ -357,13 +358,13 @@ as a command-line argument, e.g.:</p> </div> </section> <section id="sending-contributions"> -<h3>Sending contributions<a class="headerlink" href="#sending-contributions" title="Permalink to this heading">¶</a></h3> +<h3>Sending contributions<a class="headerlink" href="#sending-contributions" title="Link to this heading">¶</a></h3> <p>Changes to this document can be either submitted to <a class="reference external" href="https://bugs.gentoo.org/enter_bug.cgi?product=Documentation&component=Policy+Guide">Policy Manual Gentoo Bugzilla component</a> as git-format patches attached to the bugs, or to <a class="reference external" href="https://github.com/gentoo/policy-guide">gentoo/policy-guide repository</a> as pull requests.</p> </section> <section id="merging-pull-requests"> -<h3>Merging pull requests<a class="headerlink" href="#merging-pull-requests" title="Permalink to this heading">¶</a></h3> +<h3>Merging pull requests<a class="headerlink" href="#merging-pull-requests" title="Link to this heading">¶</a></h3> <p>The recommended way to merge pull requests is to use <code class="docutils literal notranslate"><span class="pre">app-portage/pram</span></code>. To configure the remote before the first use, run the following command in your checkout:</p> @@ -376,7 +377,7 @@ run the following command in your checkout:</p> </div> </section> <section id="publishing"> -<h3>Publishing<a class="headerlink" href="#publishing" title="Permalink to this heading">¶</a></h3> +<h3>Publishing<a class="headerlink" href="#publishing" title="Link to this heading">¶</a></h3> <p>The built version of Policy Guide is currently published via a git repository. The recommended method is to clone the repository into <code class="docutils literal notranslate"><span class="pre">_build/html</span></code> in order to make Sphinx output into the checkout:</p> @@ -389,9 +390,9 @@ into <code class="docutils literal notranslate"><span class="pre">_build/html</s </section> </section> <span id="document-dependencies"></span><section id="dependencies"> -<h2>Dependencies<a class="headerlink" href="#dependencies" title="Permalink to this heading">¶</a></h2> -<span class="target" id="index-0"></span><section id="pg0001"> -<span id="optional-runtime-dependencies"></span><span id="index-1"></span><h3>Optional runtime dependencies<a class="headerlink" href="#pg0001" title="Permalink to this heading">¶</a></h3> +<h2>Dependencies<a class="headerlink" href="#dependencies" title="Link to this heading">¶</a></h2> +<section id="pg0001"> +<span id="optional-runtime-dependencies"></span><span id="index-1"></span><span id="index-0"></span><h3>Optional runtime dependencies<a class="headerlink" href="#pg0001" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0001</p> @@ -425,7 +426,7 @@ by the Council but no reference implementation has been written.</p> </div> </section> <section id="pg0002"> -<span id="dependencies-with-no-revision"></span><span id="index-2"></span><h3>=-dependencies with no revision<a class="headerlink" href="#pg0002" title="Permalink to this heading">¶</a></h3> +<span id="dependencies-with-no-revision"></span><span id="index-2"></span><h3>=-dependencies with no revision<a class="headerlink" href="#pg0002" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0002</p> @@ -457,9 +458,9 @@ requesting the latter, it warns developers to reconsider whether they used the correct operator.</p> </section> <section id="slot-and-subslot-dependencies"> -<span id="index-3"></span><h3>Slot and subslot dependencies<a class="headerlink" href="#slot-and-subslot-dependencies" title="Permalink to this heading">¶</a></h3> +<span id="index-3"></span><h3>Slot and subslot dependencies<a class="headerlink" href="#slot-and-subslot-dependencies" title="Link to this heading">¶</a></h3> <section id="pg0011"> -<span id="on-sub-slotted-packages"></span><h4>on (sub-)slotted packages<a class="headerlink" href="#pg0011" title="Permalink to this heading">¶</a></h4> +<span id="on-sub-slotted-packages"></span><h4>on (sub-)slotted packages<a class="headerlink" href="#pg0011" title="Link to this heading">¶</a></h4> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0011</p> @@ -496,7 +497,7 @@ to the newest package version available.</p> </div> </section> <section id="pg0012"> -<span id="special-case-qt-packages"></span><span id="index-4"></span><h4>special case: Qt packages<a class="headerlink" href="#pg0012" title="Permalink to this heading">¶</a></h4> +<span id="special-case-qt-packages"></span><span id="index-4"></span><h4>special case: Qt packages<a class="headerlink" href="#pg0012" title="Link to this heading">¶</a></h4> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0012</p> @@ -518,7 +519,7 @@ if your package uses one of the private API parts, and plain <code class="docuti or likewise dependency must be used otherwise.</p> </section> <section id="proactive-use-of-slot-operators"> -<h4>proactive use of slot operators<a class="headerlink" href="#proactive-use-of-slot-operators" title="Permalink to this heading">¶</a></h4> +<h4>proactive use of slot operators<a class="headerlink" href="#proactive-use-of-slot-operators" title="Link to this heading">¶</a></h4> <p>There is an open debate on whether developers should be proactively adding <code class="docutils literal notranslate"><span class="pre">:=</span></code> slot operators on packages that do not define subslots yet.</p> @@ -532,7 +533,7 @@ They point out the case of Qt packages as an example.</p> </section> </section> <section id="pg0003"> -<span id="revision-bumps-on-runtime-dependency-changes"></span><span id="index-5"></span><h3>Revision bumps on runtime dependency changes<a class="headerlink" href="#pg0003" title="Permalink to this heading">¶</a></h3> +<span id="revision-bumps-on-runtime-dependency-changes"></span><span id="index-5"></span><h3>Revision bumps on runtime dependency changes<a class="headerlink" href="#pg0003" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0003</p> @@ -575,9 +576,9 @@ if the package installed by the user still links to libfoo.</p> </div> </section> <section id="use-dependencies"> -<span id="index-6"></span><h3>USE dependencies<a class="headerlink" href="#use-dependencies" title="Permalink to this heading">¶</a></h3> +<span id="index-6"></span><h3>USE dependencies<a class="headerlink" href="#use-dependencies" title="Link to this heading">¶</a></h3> <section id="pg0021"> -<span id="on-packages-without-the-flag"></span><h4>on packages without the flag<a class="headerlink" href="#pg0021" title="Permalink to this heading">¶</a></h4> +<span id="on-packages-without-the-flag"></span><h4>on packages without the flag<a class="headerlink" href="#pg0021" title="Link to this heading">¶</a></h4> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0021</p> @@ -618,9 +619,9 @@ updating its reverse dependencies.</p> </section> </section> <span id="document-deprecation"></span><section id="deprecations"> -<h2>Deprecations<a class="headerlink" href="#deprecations" title="Permalink to this heading">¶</a></h2> +<h2>Deprecations<a class="headerlink" href="#deprecations" title="Link to this heading">¶</a></h2> <section id="pg1001"> -<span id="deprecated-eapis"></span><span id="index-0"></span><h3>Deprecated EAPIs<a class="headerlink" href="#pg1001" title="Permalink to this heading">¶</a></h3> +<span id="deprecated-eapis"></span><span id="index-0"></span><h3>Deprecated EAPIs<a class="headerlink" href="#pg1001" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>1001</p> @@ -642,7 +643,7 @@ no version bumps are expected.</p> in <code class="docutils literal notranslate"><span class="pre">metadata/layout.conf</span></code>.</p> </section> <section id="pg1003"> -<span id="deprecated-eclasses"></span><span id="index-1"></span><h3>Deprecated eclasses<a class="headerlink" href="#pg1003" title="Permalink to this heading">¶</a></h3> +<span id="deprecated-eclasses"></span><span id="index-1"></span><h3>Deprecated eclasses<a class="headerlink" href="#pg1003" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>1003</p> @@ -662,9 +663,9 @@ inside the eclass files.</p> </section> </section> <span id="document-ebuild-format"></span><section id="ebuild-file-format"> -<h2>Ebuild file format<a class="headerlink" href="#ebuild-file-format" title="Permalink to this heading">¶</a></h2> +<h2>Ebuild file format<a class="headerlink" href="#ebuild-file-format" title="Link to this heading">¶</a></h2> <section id="pg0101"> -<span id="coding-style"></span><span id="index-0"></span><h3>Coding style<a class="headerlink" href="#pg0101" title="Permalink to this heading">¶</a></h3> +<span id="coding-style"></span><span id="index-0"></span><h3>Coding style<a class="headerlink" href="#pg0101" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0101</p> @@ -691,7 +692,7 @@ Consistency avoids unnecessary changes when other developers edit the ebuild.</p> </section> <section id="pg0102"> -<span id="code-must-be-contained-within-ebuild-and-eclasses"></span><span id="index-1"></span><h3>Code must be contained within ebuild and eclasses<a class="headerlink" href="#pg0102" title="Permalink to this heading">¶</a></h3> +<span id="code-must-be-contained-within-ebuild-and-eclasses"></span><span id="index-1"></span><h3>Code must be contained within ebuild and eclasses<a class="headerlink" href="#pg0102" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0102</p> @@ -718,7 +719,7 @@ confuses other developers and tools that do not explicitly account for that possibility, including linting tools.</p> </section> <section id="pg0103"> -<span id="homepage-must-not-contain-variables"></span><span id="index-2"></span><h3>HOMEPAGE must not contain variables<a class="headerlink" href="#pg0103" title="Permalink to this heading">¶</a></h3> +<span id="homepage-must-not-contain-variables"></span><span id="index-2"></span><h3>HOMEPAGE must not contain variables<a class="headerlink" href="#pg0103" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0103</p> @@ -740,7 +741,7 @@ preprocessing, breaking URI support in terminals and editors, as well as reducing the usefulness of plain tools such as grep.</p> </section> <section id="pg0104"> -<span id="src-uri-must-not-refer-to-homepage"></span><span id="index-3"></span><h3>SRC_URI must not refer to HOMEPAGE<a class="headerlink" href="#pg0104" title="Permalink to this heading">¶</a></h3> +<span id="src-uri-must-not-refer-to-homepage"></span><span id="index-3"></span><h3>SRC_URI must not refer to HOMEPAGE<a class="headerlink" href="#pg0104" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0104</p> @@ -763,7 +764,7 @@ it hard to copy-paste part of the URI e.g. to investigate the directory index.</p> </section> <section id="pg0105"> -<span id="keywords-must-be-defined-on-a-single-line"></span><span id="index-4"></span><h3>KEYWORDS must be defined on a single line<a class="headerlink" href="#pg0105" title="Permalink to this heading">¶</a></h3> +<span id="keywords-must-be-defined-on-a-single-line"></span><span id="index-4"></span><h3>KEYWORDS must be defined on a single line<a class="headerlink" href="#pg0105" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0105</p> @@ -784,7 +785,7 @@ ability to process and modify ebuilds, and therefore developers must make sure that it works correctly on their ebuilds.</p> </section> <section id="pg0106"> -<span id="license-must-not-contain-variables"></span><span id="index-5"></span><h3>LICENSE must not contain variables<a class="headerlink" href="#pg0106" title="Permalink to this heading">¶</a></h3> +<span id="license-must-not-contain-variables"></span><span id="index-5"></span><h3>LICENSE must not contain variables<a class="headerlink" href="#pg0106" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0106</p> @@ -805,7 +806,7 @@ package versions), using variables there has little advantage. On the other hand, variables reduce the usefulness of plain tools such as grep.</p> </section> <section id="pg0107"> -<span id="d-must-be-used-only-in-src-install-and-pkg-preinst"></span><span id="index-6"></span><h3>D must be used only in src_install and pkg_preinst<a class="headerlink" href="#pg0107" title="Permalink to this heading">¶</a></h3> +<span id="d-must-be-used-only-in-src-install-and-pkg-preinst"></span><span id="index-6"></span><h3>D must be used only in src_install and pkg_preinst<a class="headerlink" href="#pg0107" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0107</p> @@ -827,9 +828,9 @@ does not exist in other phases.</p> </section> </section> <span id="document-filesystem"></span><section id="file-system-layout"> -<h2>File system layout<a class="headerlink" href="#file-system-layout" title="Permalink to this heading">¶</a></h2> +<h2>File system layout<a class="headerlink" href="#file-system-layout" title="Link to this heading">¶</a></h2> <section id="pg0201"> -<span id="installation-paths"></span><span id="index-0"></span><h3>Installation paths<a class="headerlink" href="#pg0201" title="Permalink to this heading">¶</a></h3> +<span id="installation-paths"></span><span id="index-0"></span><h3>Installation paths<a class="headerlink" href="#pg0201" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0201</p> @@ -900,7 +901,7 @@ exceptions are:</p> </ul> </section> <section id="pg0202"> -<span id="support-for-separate-usr"></span><span id="index-1"></span><h3>Support for separate /usr<a class="headerlink" href="#pg0202" title="Permalink to this heading">¶</a></h3> +<span id="support-for-separate-usr"></span><span id="index-1"></span><h3>Support for separate /usr<a class="headerlink" href="#pg0202" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0202</p> @@ -925,7 +926,7 @@ using initramfs, some of the boot and repair functionality can be moved from rootfs to initramfs.</p> </section> <section id="pg0203"> -<span id="strict-multilib-layout"></span><span id="index-2"></span><h3>Strict multilib layout<a class="headerlink" href="#pg0203" title="Permalink to this heading">¶</a></h3> +<span id="strict-multilib-layout"></span><span id="index-2"></span><h3>Strict multilib layout<a class="headerlink" href="#pg0203" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0203</p> @@ -952,7 +953,7 @@ and packages must install libraries into appropriate directory for them to be correctly found by the dynamic loader.</p> </section> <section id="pg0204"> -<span id="static-libraries-and-libtool-files"></span><span id="index-3"></span><h3>Static libraries and libtool files<a class="headerlink" href="#pg0204" title="Permalink to this heading">¶</a></h3> +<span id="static-libraries-and-libtool-files"></span><span id="index-3"></span><h3>Static libraries and libtool files<a class="headerlink" href="#pg0204" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0204</p> @@ -978,7 +979,7 @@ used only during package builds, and installing them to rootfs would be a waste of space.</p> </section> <section id="pg0205"> -<span id="game-install-locations-and-ownership"></span><span id="index-4"></span><h3>Game install locations and ownership<a class="headerlink" href="#pg0205" title="Permalink to this heading">¶</a></h3> +<span id="game-install-locations-and-ownership"></span><span id="index-4"></span><h3>Game install locations and ownership<a class="headerlink" href="#pg0205" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0205</p> @@ -1017,7 +1018,7 @@ to the games group, a new group (gamestat) needed to be created to fulfill that purpose.</p> </section> <section id="pg0206"> -<span id="absolute-symbolic-link-targets"></span><span id="index-5"></span><h3>Absolute symbolic link targets<a class="headerlink" href="#pg0206" title="Permalink to this heading">¶</a></h3> +<span id="absolute-symbolic-link-targets"></span><span id="index-5"></span><h3>Absolute symbolic link targets<a class="headerlink" href="#pg0206" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0206</p> @@ -1048,9 +1049,9 @@ it is mounted in another location, e.g. for the purposes of recovery.</p> </section> </section> <span id="document-installed-files"></span><section id="installed-files"> -<h2>Installed files<a class="headerlink" href="#installed-files" title="Permalink to this heading">¶</a></h2> +<h2>Installed files<a class="headerlink" href="#installed-files" title="Link to this heading">¶</a></h2> <section id="pg0301"> -<span id="installation-of-small-files"></span><span id="index-0"></span><h3>Installation of small files<a class="headerlink" href="#pg0301" title="Permalink to this heading">¶</a></h3> +<span id="installation-of-small-files"></span><span id="index-0"></span><h3>Installation of small files<a class="headerlink" href="#pg0301" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0301</p> @@ -1085,7 +1086,7 @@ installed, completion files are not used at all.</p> </div> </section> <section id="pg0302"> -<span id="installation-of-static-libraries"></span><span id="index-1"></span><h3>Installation of static libraries<a class="headerlink" href="#pg0302" title="Permalink to this heading">¶</a></h3> +<span id="installation-of-static-libraries"></span><span id="index-1"></span><h3>Installation of static libraries<a class="headerlink" href="#pg0302" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0302</p> @@ -1117,7 +1118,7 @@ it is acceptable to strip static libraries in <code class="docutils literal notr </div> </section> <section id="pg0303"> -<span id="installation-of-libtool-la-files"></span><span id="index-2"></span><h3>Installation of libtool (.la) files<a class="headerlink" href="#pg0303" title="Permalink to this heading">¶</a></h3> +<span id="installation-of-libtool-la-files"></span><span id="index-2"></span><h3>Installation of libtool (.la) files<a class="headerlink" href="#pg0303" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0303</p> @@ -1151,7 +1152,7 @@ and while libtool keeps generating them, they are considered unnecessary and potentially harmful.</p> </section> <section id="pg0304"> -<span id="virtuals"></span><span id="index-3"></span><h3>Virtuals<a class="headerlink" href="#pg0304" title="Permalink to this heading">¶</a></h3> +<span id="virtuals"></span><span id="index-3"></span><h3>Virtuals<a class="headerlink" href="#pg0304" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0304</p> @@ -1171,7 +1172,7 @@ e.g., that they must not assign the <code class="docutils literal notranslate">< be impossible if they installed any files).</p> </section> <section id="pg0305"> -<span id="installation-of-manpages"></span><span id="index-4"></span><h3>Installation of manpages<a class="headerlink" href="#pg0305" title="Permalink to this heading">¶</a></h3> +<span id="installation-of-manpages"></span><span id="index-4"></span><h3>Installation of manpages<a class="headerlink" href="#pg0305" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0305</p> @@ -1194,9 +1195,9 @@ prebuilt manpages is a good compromise.</p> </section> </section> <span id="document-keywords"></span><section id="keywording-and-stabilization"> -<h2>Keywording and stabilization<a class="headerlink" href="#keywording-and-stabilization" title="Permalink to this heading">¶</a></h2> +<h2>Keywording and stabilization<a class="headerlink" href="#keywording-and-stabilization" title="Link to this heading">¶</a></h2> <section id="pg0401"> -<span id="rekeywording-on-dropped-keywords"></span><span id="index-0"></span><h3>Rekeywording on dropped keywords<a class="headerlink" href="#pg0401" title="Permalink to this heading">¶</a></h3> +<span id="rekeywording-on-dropped-keywords"></span><span id="index-0"></span><h3>Rekeywording on dropped keywords<a class="headerlink" href="#pg0401" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0401</p> @@ -1218,7 +1219,7 @@ affects other developers who in the future either want to stabilize a new version or to remove an old version.</p> </section> <section id="pg0402"> -<span id="stabilizing-new-versions"></span><span id="index-1"></span><h3>Stabilizing new versions<a class="headerlink" href="#pg0402" title="Permalink to this heading">¶</a></h3> +<span id="stabilizing-new-versions"></span><span id="index-1"></span><h3>Stabilizing new versions<a class="headerlink" href="#pg0402" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0402</p> @@ -1248,7 +1249,7 @@ is stable and whether arch teams are slacking or stabilization was not requested on remaining architectures in the first place.</p> </section> <section id="pg0403"> -<span id="removing-stable-keywords"></span><span id="index-2"></span><h3>Removing stable keywords<a class="headerlink" href="#pg0403" title="Permalink to this heading">¶</a></h3> +<span id="removing-stable-keywords"></span><span id="index-2"></span><h3>Removing stable keywords<a class="headerlink" href="#pg0403" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0403</p> @@ -1273,11 +1274,11 @@ of last rite mails.</p> </section> </section> <span id="document-languages"></span><section id="language-specific-policies"> -<h2>Language-specific policies<a class="headerlink" href="#language-specific-policies" title="Permalink to this heading">¶</a></h2> +<h2>Language-specific policies<a class="headerlink" href="#language-specific-policies" title="Link to this heading">¶</a></h2> <section id="python"> -<span id="index-0"></span><h3>Python<a class="headerlink" href="#python" title="Permalink to this heading">¶</a></h3> -<span class="target" id="index-1"></span><span class="target" id="index-2"></span><span class="target" id="index-3"></span><section id="pg0501"> -<span id="eclass-usage"></span><span id="index-4"></span><h4>Eclass usage<a class="headerlink" href="#pg0501" title="Permalink to this heading">¶</a></h4> +<span id="index-0"></span><h3>Python<a class="headerlink" href="#python" title="Link to this heading">¶</a></h3> +<section id="pg0501"> +<span id="eclass-usage"></span><span id="index-4"></span><span id="index-3"></span><span id="index-2"></span><span id="index-1"></span><h4>Eclass usage<a class="headerlink" href="#pg0501" title="Link to this heading">¶</a></h4> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0501</p> @@ -1310,7 +1311,7 @@ and variables also make it possible to gracefully retire old implementations with minimal changes to existing ebuilds.</p> </section> <section id="pg0502"> -<span id="python-2-deprecation"></span><span id="index-5"></span><h4>Python 2 deprecation<a class="headerlink" href="#pg0502" title="Permalink to this heading">¶</a></h4> +<span id="python-2-deprecation"></span><span id="index-5"></span><h4>Python 2 deprecation<a class="headerlink" href="#pg0502" title="Link to this heading">¶</a></h4> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0502</p> @@ -1346,9 +1347,9 @@ will cause major upgrade issues.</p> </section> </section> <span id="document-maintainer"></span><section id="package-maintainers"> -<h2>Package Maintainers<a class="headerlink" href="#package-maintainers" title="Permalink to this heading">¶</a></h2> +<h2>Package Maintainers<a class="headerlink" href="#package-maintainers" title="Link to this heading">¶</a></h2> <section id="pg0601"> -<span id="adding-new-maintainers"></span><span id="index-0"></span><h3>Adding new maintainers<a class="headerlink" href="#pg0601" title="Permalink to this heading">¶</a></h3> +<span id="adding-new-maintainers"></span><span id="index-0"></span><h3>Adding new maintainers<a class="headerlink" href="#pg0601" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0601</p> @@ -1377,7 +1378,7 @@ packages ended up being maintained solely by Python, and distinguishing them from packages actually within project’s profile was hard.</p> </section> <section id="pg0602"> -<span id="new-packages-without-a-maintainer"></span><span id="index-1"></span><h3>New packages without a maintainer<a class="headerlink" href="#pg0602" title="Permalink to this heading">¶</a></h3> +<span id="new-packages-without-a-maintainer"></span><span id="index-1"></span><h3>New packages without a maintainer<a class="headerlink" href="#pg0602" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0602</p> @@ -1397,9 +1398,9 @@ of packages without a maintainer. There is a small group of developers trying to fix them as necessary. It is unfair and inappropriate to increase their maintenance burden by adding new packages and refusing to take care of them.</p> -<span class="target" id="index-2"></span></section> +</section> <section id="pg0603"> -<span id="removing-package-maintainers"></span><span id="index-3"></span><h3>Removing package maintainers<a class="headerlink" href="#pg0603" title="Permalink to this heading">¶</a></h3> +<span id="removing-package-maintainers"></span><span id="index-3"></span><span id="index-2"></span><h3>Removing package maintainers<a class="headerlink" href="#pg0603" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0603</p> @@ -1431,9 +1432,9 @@ to them silently becoming maintainer-needed).</p> </section> </section> <span id="document-other-metadata"></span><section id="other-metadata-variables"> -<h2>Other metadata variables<a class="headerlink" href="#other-metadata-variables" title="Permalink to this heading">¶</a></h2> -<span class="target" id="index-0"></span><section id="pg0701"> -<span id="dynamic-slots-multislot-flag"></span><span id="index-1"></span><h3>Dynamic slots (multislot flag)<a class="headerlink" href="#pg0701" title="Permalink to this heading">¶</a></h3> +<h2>Other metadata variables<a class="headerlink" href="#other-metadata-variables" title="Link to this heading">¶</a></h2> +<section id="pg0701"> +<span id="dynamic-slots-multislot-flag"></span><span id="index-1"></span><span id="index-0"></span><h3>Dynamic slots (multislot flag)<a class="headerlink" href="#pg0701" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0701</p> @@ -1471,7 +1472,7 @@ manager behavior which could include use of unpredictable slot, cache invalidation or explicit errors.</p> </section> <section id="pg0702"> -<span id="homepage-value-must-be-meaningful"></span><span id="index-2"></span><h3>HOMEPAGE value must be meaningful<a class="headerlink" href="#pg0702" title="Permalink to this heading">¶</a></h3> +<span id="homepage-value-must-be-meaningful"></span><span id="index-2"></span><h3>HOMEPAGE value must be meaningful<a class="headerlink" href="#pg0702" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0702</p> @@ -1502,7 +1503,7 @@ those cases, using the explicit No_homepage marker at least makes it easy to identify such packages.</p> </section> <section id="pg0703"> -<span id="restrict-test-for-use-test"></span><span id="index-3"></span><h3>RESTRICT=test for USE=-test<a class="headerlink" href="#pg0703" title="Permalink to this heading">¶</a></h3> +<span id="restrict-test-for-use-test"></span><span id="index-3"></span><h3>RESTRICT=test for USE=-test<a class="headerlink" href="#pg0703" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0703</p> @@ -1536,7 +1537,7 @@ common, and there is little harm in overspecifying it.</p> </div> </section> <section id="pg0704"> -<span id="license"></span><span id="index-4"></span><h3>LICENSE<a class="headerlink" href="#pg0704" title="Permalink to this heading">¶</a></h3> +<span id="license"></span><span id="index-4"></span><h3>LICENSE<a class="headerlink" href="#pg0704" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0704</p> @@ -1584,9 +1585,9 @@ by the ebuild, e.g. init.d scripts (usually GPL-2).</p> </section> </section> <span id="document-use-flags"></span><section id="use-flags"> -<h2>USE flags<a class="headerlink" href="#use-flags" title="Permalink to this heading">¶</a></h2> +<h2>USE flags<a class="headerlink" href="#use-flags" title="Link to this heading">¶</a></h2> <section id="pg0801"> -<span id="versioned-use-flags"></span><span id="index-0"></span><h3>Versioned USE flags<a class="headerlink" href="#pg0801" title="Permalink to this heading">¶</a></h3> +<span id="versioned-use-flags"></span><span id="index-0"></span><h3>Versioned USE flags<a class="headerlink" href="#pg0801" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0801</p> @@ -1617,7 +1618,7 @@ removed since.</p> </div> </section> <section id="pg0802"> -<span id="use-gui-flag"></span><span id="index-1"></span><h3>USE=gui flag<a class="headerlink" href="#pg0802" title="Permalink to this heading">¶</a></h3> +<span id="use-gui-flag"></span><span id="index-1"></span><h3>USE=gui flag<a class="headerlink" href="#pg0802" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0802</p> @@ -1646,7 +1647,7 @@ afterwards caused issues with packages supporting a choice between multiple GUIs.</p> </section> <section id="pg0803"> -<span id="underscores-in-use-flag-names"></span><span id="index-2"></span><h3>Underscores in USE flag names<a class="headerlink" href="#pg0803" title="Permalink to this heading">¶</a></h3> +<span id="underscores-in-use-flag-names"></span><span id="index-2"></span><h3>Underscores in USE flag names<a class="headerlink" href="#pg0803" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0803</p> @@ -1680,9 +1681,9 @@ or underscores depending on developer’s personal preference.</p> </section> </section> <span id="document-user-group"></span><section id="users-and-groups"> -<h2>Users and groups<a class="headerlink" href="#users-and-groups" title="Permalink to this heading">¶</a></h2> -<span class="target" id="index-0"></span><section id="pg0901"> -<span id="user-and-group-account-policy"></span><span id="index-1"></span><h3>User and group account policy<a class="headerlink" href="#pg0901" title="Permalink to this heading">¶</a></h3> +<h2>Users and groups<a class="headerlink" href="#users-and-groups" title="Link to this heading">¶</a></h2> +<section id="pg0901"> +<span id="user-and-group-account-policy"></span><span id="index-1"></span><span id="index-0"></span><h3>User and group account policy<a class="headerlink" href="#pg0901" title="Link to this heading">¶</a></h3> <dl class="field-list simple"> <dt class="field-odd">PG<span class="colon">:</span></dt> <dd class="field-odd"><p>0901</p> @@ -1735,7 +1736,7 @@ been reserved for true system users and groups.</p> </div> </section> <section id="indices-and-tables"> -<h1>Indices and tables<a class="headerlink" href="#indices-and-tables" title="Permalink to this heading">¶</a></h1> +<h1>Indices and tables<a class="headerlink" href="#indices-and-tables" title="Link to this heading">¶</a></h1> <ul class="simple"> <li><p><a class="reference internal" href="genindex.html"><span class="std std-ref">Index</span></a></p></li> <li><p><a class="reference internal" href="search.html"><span class="std std-ref">Search Page</span></a></p></li> @@ -1904,7 +1905,7 @@ been reserved for true system users and groups.</p> <h3 class="footerhead">None</h3> <div class="row"> <div class="col-xs-12 col-md-4"> - <span class="kk-group-header">Powered by</span><br><span><a href="http://sphinx-doc.org/">Sphinx 6.2.1</a> & <a href="https://github.com/mmagorsc/tyrian_sphinx_theme">Tyrian Theme 0.0.7</a></span> + <span class="kk-group-header">Powered by</span><br><span><a href="http://sphinx-doc.org/">Sphinx 7.2.6</a> & <a href="https://github.com/mmagorsc/tyrian_sphinx_theme">Tyrian Theme 0.0.8</a></span> </div> <div class="col-xs-12 col-md-4"> </div> @@ -1918,16 +1919,13 @@ been reserved for true system users and groups.</p> </div> </div> <div class="row"> - <div class="col-xs-2 col-sm-3 col-md-2"> - <ul class="footerlinks three-icons"> - <li><a href="https://twitter.com/gentoo" title="@Gentoo on Twitter"><span class="fa fa-twitter fa-fw"></span></a></li> - <li><a href="https://www.facebook.com/gentoo.org" title="Gentoo on Facebook"><span class="fa fa-facebook fa-fw"></span></a></li> - </ul> + <div class="text-center"> + <a href="https://wiki.gentoo.org/wiki/Foundation:Privacy_Policy">Privacy Policy</a> </div> <div class="col-xs-10 col-sm-9 col-md-10"> - <strong>© 2001–2023 Gentoo Authors</strong><br> + <strong>© 2001–2024 Gentoo Authors</strong><br> <small> - Gentoo is a trademark of the Gentoo Foundation, Inc. + Gentoo is a trademark of the Gentoo Foundation, Inc. and of Förderverein Gentoo e.V. The contents of this document, unless otherwise expressly stated, are licensed under the <a href="https://creativecommons.org/licenses/by-sa/4.0/" rel="license">CC-BY-SA-4.0</a> license. The <a href="https://www.gentoo.org/inside-gentoo/foundation/name-logo-guidelines.html">Gentoo Name and Logo Usage Guidelines</a> apply. |