From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/
Date: Tue, 23 Feb 2016 07:17:27 +0000 (UTC) [thread overview]
Message-ID: <1456208958.1e6accd8734a16b896d3d529c6727ef3d3c5fd9f.ulm@gentoo> (raw)
commit: 1e6accd8734a16b896d3d529c6727ef3d3c5fd9f
Author: Vicente Jimenez Aguilar <googuy <AT> gmail <DOT> com>
AuthorDate: Mon Feb 22 13:05:41 2016 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Feb 23 06:29:18 2016 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=1e6accd8
ebuild-writing/functions: Add src_configure to the list of called functions
src_configure is missing from the list of called functions when
installing from source
ebuild-writing/functions/text.xml | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/ebuild-writing/functions/text.xml b/ebuild-writing/functions/text.xml
index d10a51f..23d68f0 100644
--- a/ebuild-writing/functions/text.xml
+++ b/ebuild-writing/functions/text.xml
@@ -6,7 +6,8 @@
<body>
<p>
When installing packages from source, the function call order is <c>pkg_setup</c>,
-<c>src_unpack</c>, <c>src_prepare</c>, <c>src_compile</c>, <c>src_test</c> (optional, <c>FEATURES="test"</c>),
+<c>src_unpack</c>, <c>src_prepare</c>, <c>src_configure</c>, <c>src_compile</c>,
+<c>src_test</c> (optional, <c>FEATURES="test"</c>),
<c>src_install</c>, <c>pkg_preinst</c>, <c>pkg_postinst</c>. When installing packages
from a binary, the function call order is <c>pkg_setup</c>, <c>pkg_preinst</c>,
<c>pkg_postinst</c>.
next reply other threads:[~2016-02-23 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 7:17 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-18 5:10 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/functions/ Sam James
2020-12-29 22:08 Göktürk Yüksek
2019-11-12 17:18 Göktürk Yüksek
2019-11-12 17:18 Göktürk Yüksek
2016-06-05 12:43 Göktürk Yüksek
2015-09-12 10:58 Markos Chandras
2014-10-18 17:35 Markos Chandras
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1456208958.1e6accd8734a16b896d3d529c6727ef3d3c5fd9f.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox