1 |
Dne pondělí 21 Září 2009 18:03:56 Torsten Veller napsal(a): |
2 |
> * Tomáš Chvátal <scarabeus@g.o>: |
3 |
> > I think it is not required |
4 |
> > EXPF="src_compile src_test src_install" <- definition, also nulls |
5 |
> > anything what was in it before :] |
6 |
> > case ${EAPI:-0} in |
7 |
> > 2) EXPF="${EXPF} src_configure" ;; |
8 |
> > 1|0) ;; |
9 |
> > *) die "Unknown EAPI, Bug eclass maintainers." ;; |
10 |
> > esac |
11 |
> > EXPORT_FUNCTIONS ${EXPF} <- export |
12 |
> |
13 |
> And later in cmake-utils_src_compile you use: |
14 |
> | has src_configure ${EXPF} || cmake-utils_src_configure |
15 |
> |
16 |
> What will happen if an EAPI=2 ebuild inherits cmake-utils and another |
17 |
> eclass also using EXPF that does not EXPORT_FUNCTIONS src_configure and |
18 |
> the ebuild uses cmake-utils_src_compile? |
19 |
> |
20 |
> It will call cmake-utils_src_configure during src_configure and later in |
21 |
> cmake-utils_src_compile it will run cmake-utils_src_configure again, |
22 |
> won't it? |
23 |
> |
24 |
You dont do this magic before inherits, so you are safe, if you inherit in |
25 |
middle of your eclass code, then you probably deserve the breakage for |
26 |
writting such horrible thing ;] |
27 |
|
28 |
|
29 |
A - inherit B |
30 |
EXPF - value from B |
31 |
A - define our own export_functions |
32 |
EXPF - value from A |