From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: [gentoo-pms] Re: EXPORT_FUNCTIONS
Date: Fri, 5 Feb 2010 21:21:11 +0100 [thread overview]
Message-ID: <19308.32183.544736.789594@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <19302.43620.26044.466404@a1i15.kph.uni-mainz.de>
>>>>> On Mon, 1 Feb 2010, I wrote:
> What is the reason for the following restriction:
> "EXPORT_FUNCTIONS must be used at most once per eclass."
If nobody knows a reason for it, then I suggest removing of this
sentence.
Ulrich
From a048b02f31a4c69fcdf0498d49eef9e387f389e3 Mon Sep 17 00:00:00 2001
From: Ulrich Mueller <ulm@gentoo.org>
Date: Fri, 5 Feb 2010 21:19:23 +0100
Subject: [PATCH] Remove restriction that EXPORT_FUNCTIONS must be used only once.
Signed-off-by: Ulrich Mueller <ulm@gentoo.org>
---
eclasses.tex | 2 --
1 files changed, 0 insertions(+), 2 deletions(-)
diff --git a/eclasses.tex b/eclasses.tex
index 9aeec91..b3ad13b 100644
--- a/eclasses.tex
+++ b/eclasses.tex
@@ -71,8 +71,6 @@ should the author wish to override it he can access the function in \t{foo.eclas
\t{EXPORT\_FUNCTIONS} must only be used on ebuild phase functions. The function that is aliased
must be named \t{eclassname\_phasefunctionname}, where \t{eclassname} is the name of the eclass.
-\t{EXPORT\_FUNCTIONS} must be used at most once per eclass.
-
% vim: set filetype=tex fileencoding=utf8 et tw=100 spell spelllang=en :
%%% Local Variables:
--
1.6.6.1
next prev parent reply other threads:[~2010-02-05 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-17 12:39 [gentoo-pms] Fill column Ulrich Mueller
2010-01-17 14:26 ` Ciaran McCreesh
2010-01-19 12:06 ` Brian Harring
2010-01-19 12:26 ` David Leverton
2010-02-01 10:18 ` [gentoo-pms] EXPORT_FUNCTIONS Ulrich Mueller
2010-02-05 20:21 ` Ulrich Mueller [this message]
2010-02-05 21:22 ` [gentoo-pms] EXPORT_FUNCTIONS David Leverton
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=19308.32183.544736.789594@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-pms@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