commit: 90fa2a619b36681a02458fb07ba9670a87a6b91e Author: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> AuthorDate: Sat Jun 18 22:14:43 2016 +0000 Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org> CommitDate: Sat Jun 18 22:14:43 2016 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=90fa2a61
ebuild-writing/.../epatch: use the term 'inherit' as opposed to import Reported-by: Amy Winston <amynka <AT> gentoo.org> ebuild-writing/functions/src_prepare/epatch/text.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ebuild-writing/functions/src_prepare/epatch/text.xml b/ebuild-writing/functions/src_prepare/epatch/text.xml index a3adfb5..6cdff0d 100644 --- a/ebuild-writing/functions/src_prepare/epatch/text.xml +++ b/ebuild-writing/functions/src_prepare/epatch/text.xml @@ -7,7 +7,7 @@ <p> The canonical way of applying patches in ebuilds is to use <c>epatch</c> (from <c>eutils.eclass</c>, which you must make sure -to import!) inside <c>src_prepare</c>. This function automatically +to inherit!) inside <c>src_prepare</c>. This function automatically handles <c>-p</c> levels, <c>gunzip</c> and so on as necessary. Also note that olds ebuild may still use src_unpack to apply patches. This is because those ebuilds are based in EAPI=1. You are advised to use EAPI=2 and apply your patches in src_prepare function instead. </p>
