>>>>> 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@g.o>
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@g.o>
---
 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