public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/
Date: Fri, 12 Mar 2021 20:42:22 +0000 (UTC)	[thread overview]
Message-ID: <1615581732.59c460dd367e04cd76eb4dacbca9686e22370d18.ulm@gentoo> (raw)

commit:     59c460dd367e04cd76eb4dacbca9686e22370d18
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Mar 12 18:18:30 2021 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Fri Mar 12 20:42:12 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=59c460dd

appendices/common-problems: update eapi7-ver reference

We should refer to them as just built-in helpers now. Note that the linked
page references these anyway, so no need to describe them again.

Closes: https://github.com/gentoo/devmanual/pull/201
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>

 appendices/common-problems/text.xml | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/appendices/common-problems/text.xml b/appendices/common-problems/text.xml
index b4fd3ea..a2af22a 100644
--- a/appendices/common-problems/text.xml
+++ b/appendices/common-problems/text.xml
@@ -57,11 +57,10 @@ in use, there are various alternatives:
   </dt>
   <dd>
     Usually when any of the above are used in global scope, it is to manipulate
-    a version or program name string. These should be avoided in favour of
-    pure <c>bash</c> constructs. The <c>eapi7-ver</c> eclass is often of use here.
-    See <uri link="::ebuild-writing/variables/#Version and Name Formatting Issues"/>,
-    <c>man eapi7-ver.eclass</c> and <uri
-    link="::tools-reference/bash/#Bash Variable Manipulation"/>.
+    a version or program name string. These should be avoided in favour of pure
+    <c>bash</c> constructs. The built-in helpers of EAPI 7 are useful here. See
+    <uri link="::ebuild-writing/variables/#Version and Name Formatting Issues"/>
+    and <uri link="::tools-reference/bash/#Bash Variable Manipulation"/>.
   </dd>
   <dt>
     <c>has_version</c>, <c>best_version</c>


             reply	other threads:[~2021-03-12 20:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-12 20:42 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-24  9:49 [gentoo-commits] proj/devmanual:master commit in: appendices/common-problems/ Ulrich Müller
2022-06-24  9:49 Ulrich Müller
2016-05-15  1:24 Göktürk Yüksek
2016-05-04  9:13 Göktürk Yüksek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1615581732.59c460dd367e04cd76eb4dacbca9686e22370d18.ulm@gentoo \
    --to=ulm@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox