diff options
authorUlrich Müller <ulm@gentoo.org>2020-01-15 19:46:10 +0100
committerUlrich Müller <ulm@gentoo.org>2020-01-15 22:28:47 +0100
commitdcc14c2f62399bab71d7b22b41c2e8f449a0c515 (patch)
parentdevbook-guide: Section on including sub-documents. (diff)
Use source form of URI fragment identifiers throughout.
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
9 files changed, 15 insertions, 15 deletions
diff --git a/ebuild-maintenance/maintenance-tasks/text.xml b/ebuild-maintenance/maintenance-tasks/text.xml
index 4affaea..0de2f6d 100644
--- a/ebuild-maintenance/maintenance-tasks/text.xml
+++ b/ebuild-maintenance/maintenance-tasks/text.xml
@@ -38,7 +38,7 @@ files should be placed in the <c>mycat/mypkg/files</c> directory
to keep the main <c>mycat/mypkg</c> directory uncluttered.
Exceptions to this rule are for larger patch files (we recommend this
for patches above 20KB) which should be distributed as tarballs via the
-<uri link="::general-concepts/mirrors/#suitable-download-hosts">Gentoo
+<uri link="::general-concepts/mirrors/#Suitable Download Hosts">Gentoo
mirror system</uri> so that people do not waste excessive amounts of
bandwidth and hard drive space. Also, you should not add binary
(non-ASCII) files to the git tree. Also, speaking of merging changes,
diff --git a/ebuild-writing/eapi/text.xml b/ebuild-writing/eapi/text.xml
index f1bdfed..642cfe7 100644
--- a/ebuild-writing/eapi/text.xml
+++ b/ebuild-writing/eapi/text.xml
@@ -1094,7 +1094,7 @@ src_install() {
<li><p><c>ver_rs</c> replaces separators in a version string</p></li>
<li><p><c>ver_test</c> compares two versions</p></li>
- <p>See <uri link="::ebuild-writing/variables#version-and-name-formatting-issues">Version and Name Formatting Issues</uri>
+ <p>See <uri link="::ebuild-writing/variables/#Version and Name Formatting Issues"/>
for examples of common uses or
<uri link="https://dev.gentoo.org/~mgorny/articles/the-ultimate-guide-to-eapi-7.html#version-manipulation-and-comparison-commands">
an in-depth look</uri></p>
diff --git a/ebuild-writing/file-format/text.xml b/ebuild-writing/file-format/text.xml
index cc125b8..e899f7b 100644
--- a/ebuild-writing/file-format/text.xml
+++ b/ebuild-writing/file-format/text.xml
@@ -124,7 +124,7 @@ is $(upcoming-version)_preYYYYMMDD.
The policy for so-called <e>live</e> ebuilds
-(see <uri link="::ebuild-writing/functions/src_unpack/#src_unpack-actions"/>)
+(see <uri link="::ebuild-writing/functions/src_unpack/#src_unpack Actions"/>)
is to use <c>9999</c> as the version (or as the last version component).
diff --git a/ebuild-writing/functions/src_prepare/epatch/text.xml b/ebuild-writing/functions/src_prepare/epatch/text.xml
index 59987fc..ad05830 100644
--- a/ebuild-writing/functions/src_prepare/epatch/text.xml
+++ b/ebuild-writing/functions/src_prepare/epatch/text.xml
@@ -100,7 +100,7 @@ src_unpack() {
For larger patches, using
-<uri link="::general-concepts/mirrors/#suitable-download-hosts">
+<uri link="::general-concepts/mirrors/#Suitable Download Hosts">
your devspace</uri> rather than
<uri link="::ebuild-writing/variables#Predefined Read-Only Variables">
${FILESDIR}</uri> is more appropriate. In these situations, it is
diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml
index 54b7bd2..d7f883a 100644
--- a/ebuild-writing/misc-files/metadata/text.xml
+++ b/ebuild-writing/misc-files/metadata/text.xml
@@ -79,7 +79,7 @@ metadata.xml:
This tag contains a description for a category or a package. For
packages, it is used to augment the
- <uri link="::ebuild-writing/variables#ebuild-defined-variables">
+ <uri link="::ebuild-writing/variables/#Ebuild-defined Variables">
DESCRIPTION</uri> field in the ebuilds themselves. This tag has
two optional subtags: <c>&lt;pkg&gt;</c> and <c>&lt;cat&gt;</c>.
@@ -143,8 +143,8 @@ metadata.xml:
- This tag contains descriptions of <uri
- link="::ebuild-writing/variables#iuse">USE flags</uri>.
+ This tag contains descriptions of
+ <uri link="::ebuild-writing/variables/#IUSE">USE flags</uri>.
This tag is optional and, if specified, has one required subtag:
@@ -294,7 +294,7 @@ There are also some attributes that can be used with these tags:
When this attribute is required on the &lt;flag&gt; tag, it
simply contains the name of the USE flag. For the
&lt;slot&gt; tag, it specifies the
- <uri link="::general-concepts/slotting#slot-names">
+ <uri link="::general-concepts/slotting/#Slot Names">
slot name</uri> to which it applies. A slot name of <c>"*"</c>
allows for a single &lt;slot&gt; tag to match all the slots of a
package, in which case no other slot tags may be present.
diff --git a/ebuild-writing/misc-files/patches/text.xml b/ebuild-writing/misc-files/patches/text.xml
index 8e87c2c..87cc328 100644
--- a/ebuild-writing/misc-files/patches/text.xml
+++ b/ebuild-writing/misc-files/patches/text.xml
@@ -25,7 +25,7 @@ number in the patch name as a suffix to the version part <d/>
Larger patches should be
-<uri link="::general-concepts/mirrors/#suitable-download-hosts">
+<uri link="::general-concepts/mirrors/#Suitable Download Hosts">
mirrored</uri>, preferably on the Gentoo Infrastructure. When
mirroring patches, choosing a name that will not cause conflicts is
important — the <c>${P}</c> prefix is highly recommended
diff --git a/ebuild-writing/variables/text.xml b/ebuild-writing/variables/text.xml
index 7e1d37b..b9310a1 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -301,7 +301,7 @@ The following variables may or must be defined by every ebuild.
An array or space-delimited list of documentation files for
the default src_install function to install using dodoc. If
undefined, a reasonable default list is used. (Requires
- <uri link="::ebuild-writing/eapi/#eapi=4">EAPI>=4</uri>.)
+ <uri link="::ebuild-writing/eapi/#EAPI=4">EAPI&gt;=4</uri>.)
@@ -310,7 +310,7 @@ The following variables may or must be defined by every ebuild.
An array or space-delimited list of documentation files or
directories for the <c>einstalldocs</c> function to install
recursively. (Requires
- <uri link="::ebuild-writing/eapi/#eapi=6">EAPI>=6</uri>.)
+ <uri link="::ebuild-writing/eapi/#EAPI=6">EAPI&gt;=6</uri>.)
@@ -752,7 +752,7 @@ Finally, to state "at least one of foo, bar, or baz must be set":
REQUIRED_USE="|| ( foo bar baz )"
-See section <uri link="::general-concepts/use-flags/#conflicting-use-flags" />
+See section <uri link="::general-concepts/use-flags/#Conflicting USE Flags"/>
for when (and when not) to use <c>REQUIRED_USE</c>.
diff --git a/general-concepts/mirrors/text.xml b/general-concepts/mirrors/text.xml
index 9319012..409ff57 100644
--- a/general-concepts/mirrors/text.xml
+++ b/general-concepts/mirrors/text.xml
@@ -154,8 +154,8 @@ doing so can cause all kinds of problems with strict firewalls.
Usage of third-party mirrors and the <c>mirror://</c>
- pseudo-protocol is described in the <uri
- link="::ebuild-writing/variables/#third-party-mirrors"><c>SRC_URI</c>
+ pseudo-protocol is described in the
+ <uri link="::ebuild-writing/variables/#Third-party mirrors"><c>SRC_URI</c>
variable documentation</uri>.
diff --git a/general-concepts/use-flags/text.xml b/general-concepts/use-flags/text.xml
index b880fa4..772791f 100644
--- a/general-concepts/use-flags/text.xml
+++ b/general-concepts/use-flags/text.xml
@@ -291,7 +291,7 @@ src_compile() {
In some exceptional cases, above policy would break reverse USE
dependencies. To avoid this, the ebuild can specify allowed USE flag
combinations with <c>REQUIRED_USE</c> (available in EAPI 4). See section
-<uri link="::ebuild-writing/eapi/#eapi=4" /> for a description
+<uri link="::ebuild-writing/eapi/#EAPI=4"/> for a description
of its syntax.