ebuild-writing/eapi: Move EAPI=2 information to other sections.

- doman language support: incorporated into
  function-reference/install-functions
- Blockers incorporated into general-concepts/dependencies
  (also say "weak" and "strong" blockers instead of "soft" and "hard",
  in order to agree with the terms used in PMS)
- USE dependencies: already in general-concepts/dependencies
- SRC_URI arrows: incorporated into ebuild-writing/variables
- src_prepare: already in ebuild-writing/functions/src_prepare
- src_configure: already in ebuild-writing/functions/src_configure
- Execution order: already in ebuild-writing/functions
- Default phase functions moved to ebuild-writing/functions

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

1 files changed, 2 insertions, 21 deletions

diff --git a/ebuild-writing/functions/src_prepare/epatch/text.xml b/ebuild-writing/functions/src_prepare/epatch/text.xml
index ad05830..d1def03 100644
--- a/ebuild-writing/functions/src_prepare/epatch/text.xml
+++ b/ebuild-writing/functions/src_prepare/epatch/text.xml
@@ -12,12 +12,6 @@ handles <c>-p</c> levels, <c>gunzip</c> and so on as necessary.
 </p>
 
 <p>
-Also note that old ebuilds may still use src_unpack to apply patches.
-This is because those ebuilds are based in EAPI=1.
-You are advised to use the latest and apply your patches in src_prepare function instead.
-</p>
-
-<p>
 Starting with EAPI=7, this function is banned and <c>eapply</c> must be used.
 </p>
 
@@ -90,9 +84,7 @@ fails. The following is taken from <c>app-misc/detox</c>:
 </p>
 
 <codesample lang="ebuild">
-src_unpack() {
-	unpack ${A}
-	cd "${S}"
+src_prepare() {
 	epatch "${FILESDIR}/${P}-destdir.patch"
 	epatch "${FILESDIR}/${P}-parallel_build.patch"
 }
@@ -110,15 +102,6 @@ be compressed). For example, from <c>app-admin/showconsole</c>:
 </p>
 
 <codesample lang="ebuild">
-src_unpack() {
-	unpack ${A}
-	cd "${S}"
-	epatch "${WORKDIR}/${P}-suse-update.patch.bz2"
-	epatch "${FILESDIR}/${PV}-no-TIOCGDEV.patch"
-}
-</codesample>
-<p>As stated before, if you are using EAPI >=2, you should apply the patches in the <uri link="::ebuild-writing/functions/src_prepare">src_prepare</uri> function</p>
-<codesample lang="ebuild">
 src_prepare() {
 	epatch "${WORKDIR}/${P}-suse-update.patch.bz2"
 	epatch "${FILESDIR}/${PV}-no-TIOCGDEV.patch"
@@ -146,9 +129,7 @@ A simple example:
 </p>
 
 <codesample lang="ebuild">
-src_unpack() {
-	unpack ${A}
-	cd "${S}"
+src_prepare() {
 	EPATCH_SOURCE="${WORKDIR}/patches" EPATCH_SUFFIX="patch" \
 		EPATCH_FORCE="yes" epatch
 }