commit: f7cc34083e1b3447dde176963f98c1bf50b29f0b Author: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> AuthorDate: Tue Dec 29 02:40:34 2020 +0000 Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> CommitDate: Tue Dec 29 22:07:30 2020 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=f7cc3408
eclass-writing: prefer "phase functions" over "ebuild functions" When the text specifically refers to phase functions, be more verbose about it. Ebuilds can define other functions that are internal. Eclasses also define functions. Using the term "phase functions" should help clarify the ambiguity. Signed-off-by: Göktürk Yüksek <gokturk <AT> gentoo.org> Closes: https://github.com/gentoo/devmanual/pull/183 eclass-writing/text.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/eclass-writing/text.xml b/eclass-writing/text.xml index 6598f9a..d0048b3 100644 --- a/eclass-writing/text.xml +++ b/eclass-writing/text.xml @@ -643,7 +643,7 @@ domacosapp() { <body> <p> -An eclass may provide default implementations for any of the standard ebuild +An eclass may provide default implementations for any of the ebuild phase functions (<c>src_unpack</c>, <c>pkg_postinst</c> etc). This can be done either as a simple function definition (which is not multiple eclass friendly) or using <c>EXPORT_FUNCTIONS</c>. Functions given to <c>EXPORT_FUNCTIONS</c> are implemented @@ -651,7 +651,7 @@ as normal, but have their name prefixed with <c>${ECLASS}_</c>. </p> <important> -Only 'standard' functions should be specified in <c>EXPORT_FUNCTIONS</c>. +Only the ebuild phase functions may be specified in <c>EXPORT_FUNCTIONS</c>. </important> <note><c>EXPORT_FUNCTIONS</c> is a function, <e>not</e> a variable.</note>
