[gentoo-commits] proj/devmanual:master commit in: keywording/

["Ulrich Müller" <ulm@gentoo.org>]

commit:     6b5ff53adca1ad2fe5b3f9b2bb35245fd507ffab
Author:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 10 10:09:26 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Oct 13 13:40:35 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=6b5ff53a

keywording: add ekeyword ~all command example

Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 keywording/text.xml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/keywording/text.xml b/keywording/text.xml
index 74bca5d..cc10166 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -201,9 +201,11 @@ Do <b>not</b> commit straight to <c>arch</c> ("stable").
 
 <p>
 When upgrading, drop all existing keywords from <c>arch</c> to <c>~arch</c>
-("testing"), and leave any existing <c>~arch</c> keywords intact. This must be
-done even if you <e>think</e> you're just making a trivial fix <d /> there have
-been several examples of the stable tree getting broken this way.
+("testing"), and leave any existing <c>~arch</c> keywords intact. It's easiest
+and safest to use <c>ekeyword ~all my-new-version.ebuild</c> from the <c>
+app-portage/gentoolkit</c> package. This must be done even if you <e>think</e>
+you're just making a trivial fix <d /> there have been several examples of the
+stable tree getting broken this way.
 </p>
 
 <p>