From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/
Date: Fri, 18 Jun 2021 05:10:04 +0000 (UTC) [thread overview]
Message-ID: <1623992921.4346ec7a970d45423d7bf72d01710c805e2413e0.sam@gentoo> (raw)
commit: 4346ec7a970d45423d7bf72d01710c805e2413e0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Apr 10 02:26:29 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jun 18 05:08:41 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=4346ec7a
ebuild-writing/functions: mention defining phases in the canonical order
This aids readability.
Signed-off-by: Sam James <sam <AT> gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/224
Signed-off-by: Sam James <sam <AT> gentoo.org>
ebuild-writing/functions/text.xml | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/ebuild-writing/functions/text.xml b/ebuild-writing/functions/text.xml
index b15c0b1..b4c3378 100644
--- a/ebuild-writing/functions/text.xml
+++ b/ebuild-writing/functions/text.xml
@@ -16,6 +16,11 @@ As some phases haven't been introduced from the beginning, you can have a look a
<uri link="::ebuild-writing/eapi"/> for an overview, what have been introduced in which EAPI.
</p>
+<p>
+Ebuilds should usually define phases in the order they are called,
+as set out above, for readability.
+</p>
+
<figure short="How the ebuild phase functions are processed" link="diagram.png"/>
<p>
next reply other threads:[~2021-06-18 5:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 5:10 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-29 22:08 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/ Göktürk Yüksek
2019-11-12 17:18 Göktürk Yüksek
2019-11-12 17:18 Göktürk Yüksek
2016-06-05 12:43 Göktürk Yüksek
2016-02-23 7:17 Ulrich Müller
2015-09-12 10:58 Markos Chandras
2014-10-18 17:35 Markos Chandras
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=1623992921.4346ec7a970d45423d7bf72d01710c805e2413e0.sam@gentoo \
--to=sam@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