[gentoo-commits] proj/devmanual:master commit in: general-concepts/autotools/

["Markos Chandras" <hwoarang@gentoo.org>]

commit:     6caf536344d33440901d7238fb2ee14bc856d2b4
Author:     Michael Orlitzky <michael <AT> orlitzky <DOT> com>
AuthorDate: Sat Sep  7 18:44:49 2013 +0000
Commit:     Markos Chandras <hwoarang <AT> gentoo <DOT> org>
CommitDate: Sat Sep  7 19:12:08 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=6caf5363

Update an old suggestion in the Autotools Basics guide.

Fixes bug #484104.

---
 general-concepts/autotools/text.xml | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/general-concepts/autotools/text.xml b/general-concepts/autotools/text.xml
index 181940c..6fb7bd8 100644
--- a/general-concepts/autotools/text.xml
+++ b/general-concepts/autotools/text.xml
@@ -76,10 +76,20 @@ and have the same format <d/> the only difference is the name.
 </note>
 
 <p>
-You will see autotools being used variously in both <c>src_unpack</c> and
-<c>src_compile</c>. The QA people prefer it in <c>src_unpack</c> <d/> the rationale is
-that <c>src_unpack</c> handles "getting the package ready to be compiled" <d/> but
-there is no official policy which mandates this.
+  You may see autotools being used in a variety of phase
+  functions. Prior to EAPI2, the QA team preferred that the source
+  code be manipulated in <c>src_unpack</c><d/>the rationale being that
+  <c>src_unpack</c> handles "getting the package ready to be
+  compiled."
+</p>
+
+<p>
+  EAPI2, however, introduced a new phase function: <uri
+  link="::ebuild-writing/functions/src_prepare" />. This is now the
+  appropriate place to manipulate the source code prior to
+  configuration and compilation. In particular, <c>src_prepare</c> is
+  called before <uri link="::ebuild-writing/functions/src_configure"
+  />, which usually expects the <c>configure</c> script to exist.
 </p>
 
 <p>