commit: af2d6c1be5c8da16693a5fc2a0fe39bbf9768cf5
Author: Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 6 14:07:42 2025 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Mon Sep 15 08:42:18 2025 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=af2d6c1b
*: fix uris linking keywording
Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
archs/sparc/text.xml | 2 +-
ebuild-writing/variables/text.xml | 4 ++--
general-concepts/ebuild-revisions/text.xml | 2 +-
quickstart/text.xml | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/archs/sparc/text.xml b/archs/sparc/text.xml
index fccce39..6844749 100644
--- a/archs/sparc/text.xml
+++ b/archs/sparc/text.xml
@@ -55,7 +55,7 @@ buses.
<note>
This section is in addition to the guidelines in
-<uri link="::keywording/#Keywording on upgrades"/>. It discusses
+<uri link="::keywording/workflow/#Keywording on upgrades"/>. It discusses
<e>additional</e> requirements for the SPARC architecture.
</note>
diff --git a/ebuild-writing/variables/text.xml
b/ebuild-writing/variables/text.xml
index 7b6ffe8..7f94a47 100644
--- a/ebuild-writing/variables/text.xml
+++ b/ebuild-writing/variables/text.xml
@@ -307,7 +307,7 @@ The following variables may or must be defined by every
ebuild.
<ti><c>KEYWORDS</c></ti>
<ti>
See <uri link="::ebuild-writing/variables/#KEYWORDS"/> and
- <uri link="::keywording/"/>.
+ <uri link="::keywording/concepts/"/>.
</ti>
</tr>
<tr>
@@ -608,7 +608,7 @@ The only valid construct involving a <c>*</c> inside
<c>KEYWORDS</c> is a <c>-*<
</p>
<p>
-See <uri link="::keywording/"/> for how to handle this variable.
+See <uri link="::keywording/concepts/"/> for how to handle this variable.
</p>
</body>
diff --git a/general-concepts/ebuild-revisions/text.xml
b/general-concepts/ebuild-revisions/text.xml
index f3054a4..65c7452 100644
--- a/general-concepts/ebuild-revisions/text.xml
+++ b/general-concepts/ebuild-revisions/text.xml
@@ -46,7 +46,7 @@ of thumb could be used as a guideline:
<li>
If the package has stable keywords, then a new revision should be
introduced for every non-trivial change, and its keywords should be dropped
- to <c>~arch</c> (see <uri link="::keywording/#Keywording on upgrades"/>).
+ to <c>~arch</c> (see <uri link="::keywording/workflow/#Keywording on
upgrades"/>).
The general guideline here is conservatism and the need to minimize
the risk of accidental breakage for stable users.
</li>
diff --git a/quickstart/text.xml b/quickstart/text.xml
index 325e08c..38e6e46 100644
--- a/quickstart/text.xml
+++ b/quickstart/text.xml
@@ -126,7 +126,7 @@ If you've not seen slots before, either just use <c>"0"</c>
or read
The <c>KEYWORDS</c> variable is set to archs upon which this ebuild has been
tested. We use <c>~</c> keywords for newly written ebuilds <d/> packages are
not
committed straight to stable, even if they seem to work.
-See <uri link="::keywording/"/> for details.
+See <uri link="::keywording/concepts/"/> for details.
</p>
</body>
</subsection>
