1 |
>>>>> On Mon, 1 Feb 2010, I wrote: |
2 |
|
3 |
> What is the reason for the following restriction: |
4 |
> "EXPORT_FUNCTIONS must be used at most once per eclass." |
5 |
|
6 |
If nobody knows a reason for it, then I suggest removing of this |
7 |
sentence. |
8 |
|
9 |
Ulrich |
10 |
|
11 |
|
12 |
From a048b02f31a4c69fcdf0498d49eef9e387f389e3 Mon Sep 17 00:00:00 2001 |
13 |
From: Ulrich Mueller <ulm@g.o> |
14 |
Date: Fri, 5 Feb 2010 21:19:23 +0100 |
15 |
Subject: [PATCH] Remove restriction that EXPORT_FUNCTIONS must be used only once. |
16 |
|
17 |
|
18 |
Signed-off-by: Ulrich Mueller <ulm@g.o> |
19 |
--- |
20 |
eclasses.tex | 2 -- |
21 |
1 files changed, 0 insertions(+), 2 deletions(-) |
22 |
|
23 |
diff --git a/eclasses.tex b/eclasses.tex |
24 |
index 9aeec91..b3ad13b 100644 |
25 |
--- a/eclasses.tex |
26 |
+++ b/eclasses.tex |
27 |
@@ -71,8 +71,6 @@ should the author wish to override it he can access the function in \t{foo.eclas |
28 |
\t{EXPORT\_FUNCTIONS} must only be used on ebuild phase functions. The function that is aliased |
29 |
must be named \t{eclassname\_phasefunctionname}, where \t{eclassname} is the name of the eclass. |
30 |
|
31 |
-\t{EXPORT\_FUNCTIONS} must be used at most once per eclass. |
32 |
- |
33 |
% vim: set filetype=tex fileencoding=utf8 et tw=100 spell spelllang=en : |
34 |
|
35 |
%%% Local Variables: |
36 |
-- |
37 |
1.6.6.1 |