1 |
commit: 4346ec7a970d45423d7bf72d01710c805e2413e0 |
2 |
Author: Sam James <sam <AT> gentoo <DOT> org> |
3 |
AuthorDate: Sat Apr 10 02:26:29 2021 +0000 |
4 |
Commit: Sam James <sam <AT> gentoo <DOT> org> |
5 |
CommitDate: Fri Jun 18 05:08:41 2021 +0000 |
6 |
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=4346ec7a |
7 |
|
8 |
ebuild-writing/functions: mention defining phases in the canonical order |
9 |
|
10 |
This aids readability. |
11 |
|
12 |
Signed-off-by: Sam James <sam <AT> gentoo.org> |
13 |
Closes: https://github.com/gentoo/devmanual/pull/224 |
14 |
Signed-off-by: Sam James <sam <AT> gentoo.org> |
15 |
|
16 |
ebuild-writing/functions/text.xml | 5 +++++ |
17 |
1 file changed, 5 insertions(+) |
18 |
|
19 |
diff --git a/ebuild-writing/functions/text.xml b/ebuild-writing/functions/text.xml |
20 |
index b15c0b1..b4c3378 100644 |
21 |
--- a/ebuild-writing/functions/text.xml |
22 |
+++ b/ebuild-writing/functions/text.xml |
23 |
@@ -16,6 +16,11 @@ As some phases haven't been introduced from the beginning, you can have a look a |
24 |
<uri link="::ebuild-writing/eapi"/> for an overview, what have been introduced in which EAPI. |
25 |
</p> |
26 |
|
27 |
+<p> |
28 |
+Ebuilds should usually define phases in the order they are called, |
29 |
+as set out above, for readability. |
30 |
+</p> |
31 |
+ |
32 |
<figure short="How the ebuild phase functions are processed" link="diagram.png"/> |
33 |
|
34 |
<p> |