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: eclass-writing/
Date: Mon, 06 Jan 2025 21:37:25 +0000 (UTC)	[thread overview]
Message-ID: <1736080651.2db21f800191f00cafb5ce90f31e28041628d33c.ulm@gentoo> (raw)

commit:     2db21f800191f00cafb5ce90f31e28041628d33c
Author:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sun Jan  5 12:08:49 2025 +0000
Commit:     Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Jan  5 12:37:31 2025 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=2db21f80

eclass-writing: Specify @BLURB more precisely

The @BLURB description appears in the NAME section of the generated
man page, and should therefore follow the rules from man-pages(7):

"All words in this line (including the word immediately following the
'\-') should be in lowercase, except where English or technical
terminological convention dictates otherwise."

Since it is a section heading, it should not end with a full stop
either.

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

 eclass-writing/text.xml | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml
index d115b8b..9af74ea 100644
--- a/eclass-writing/text.xml
+++ b/eclass-writing/text.xml
@@ -266,8 +266,9 @@ summarizes the available documentation tags:
   <ti>Yes</ti>
   <ti>Single line freetext</ti>
   <ti>
-    Contains a short description for the eclass. Must be on the same
-    line with the tag.
+    Contains a short description for the eclass. Must be on the same line
+    as the tag. All words, including the first, must be in lowercase, except
+    for proper nouns. The description must <e>not</e> end with a full stop.
   </ti>
 </tr>
 <tr>
@@ -578,13 +579,13 @@ a single function, <c>domacosapp</c>.
 </p>
 
 <codesample lang="ebuild">
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 # @ECLASS: macosapp.eclass
 # @MAINTAINER:
 # Ciaran McCreesh &lt;ciaranm@gentoo.org&gt;
-# @BLURB: install macos .app files to the relevant location.
+# @BLURB: install macos .app files to the relevant location
 
 # @FUNCTION: domacosapp
 # @USAGE: &lt;app-file&gt; [new-file]
@@ -746,14 +747,14 @@ for an eclass to invoke die from the global scope.  For example:
 </p>
 
 <codesample lang="ebuild">
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 # @ECLASS: eapi-die.eclass
 # @MAINTAINER:
 # Gentoo Devmanual Project &lt;devmanual@gentoo.org&gt;
 # @SUPPORTED_EAPIS: 7 8
-# @BLURB: Calls die when used with an invalid EAPI.
+# @BLURB: call die when used with an invalid EAPI
 
 case ${EAPI} in
 	7|8) ;;
@@ -775,7 +776,7 @@ functions.
 </p>
 
 <codesample lang="ebuild">
-# Copyright 1999-2022 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 # @ECLASS: jmake.eclass
@@ -783,7 +784,7 @@ functions.
 # Gentoo Devmanual Project &lt;devmanual@gentoo.org&gt;
 # @AUTHOR:
 # Ciaran McCreesh &lt;ciaranm@gentoo.org&gt;
-# @BLURB: Demonstrate a simple build system eclass.
+# @BLURB: demonstrate a simple build system eclass
 # @DESCRIPTION:
 # Demonstrates EXPORT_FUNCTIONS and defines simple wrappers for the
 # (hypothetical) jmake build system along with default src_configure and


             reply	other threads:[~2025-01-06 21:37 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-06 21:37 Ulrich Müller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-29  6:31 [gentoo-commits] proj/devmanual:master commit in: eclass-writing/ Ulrich Müller
2024-04-29  6:31 Ulrich Müller
2024-04-29  6:31 Ulrich Müller
2024-04-29  6:31 Ulrich Müller
2024-01-19 21:06 Ulrich Müller
2023-08-26  5:30 Ulrich Müller
2023-05-27 18:49 Ulrich Müller
2022-04-30 17:01 Ulrich Müller
2022-04-28  8:12 Ulrich Müller
2022-04-24 12:52 Ulrich Müller
2022-03-26 16:16 Ulrich Müller
2022-03-23 14:10 Ulrich Müller
2022-03-20 13:48 Ulrich Müller
2022-03-18 18:10 Sam James
2022-03-18 18:10 Sam James
2022-03-16 14:47 Sam James
2022-03-16 14:47 Sam James
2021-12-09  5:01 Sam James
2021-10-13 13:44 Ulrich Müller
2021-09-04 10:38 Ulrich Müller
2021-09-04 10:36 Ulrich Müller
2021-09-04 10:36 Ulrich Müller
2021-09-04 10:33 Ulrich Müller
2021-09-04 10:33 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2021-03-30  6:55 Ulrich Müller
2020-12-29 22:08 Göktürk Yüksek
2020-09-18  7:01 Ulrich Müller
2019-09-20 22:52 Göktürk Yüksek
2019-08-30 15:51 Göktürk Yüksek
2019-08-30 15:51 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2016-10-31  1:21 Göktürk Yüksek
2011-12-13 20:17 Petteri Räty

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=1736080651.2db21f800191f00cafb5ce90f31e28041628d33c.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