Gentoo Archives: gentoo-java

From: Vlastimil Babka <caster@g.o>
To: gentoo-java@l.g.o
Subject: Re: [gentoo-java] generation-2 java eclass
Date: Thu, 21 Sep 2006 18:00:22
Message-Id: 4512D2C4.4000908@gentoo.org
In Reply to: Re: [gentoo-java] generation-2 java eclass by Alon Bar-Lev
1 Alon Bar-Lev wrote:
2 > Looking at bug#146647, why did you remove the java from the IUSE? I
3
4 Because the eclass provides it already. Ebuild doesn't need to.
5
6 > don't think it is a clean to require programmer to define the
7 > JAVA_PKG_OPT_USE before the inherit... Or you need to add a BIG FAT
8 > WARNING at the eclass documentation/description.
9
10 You're getting it wrong. JAVA_PKG_OPT_USE is just a name for the flag
11 that triggers java support. You need to specify it before inherit line
12 if you want the flag to be called differently than "java" (the default).
13 Not sure if any ebuild ever overrided that, it's just the possibility.
14
15 > And shouldn't the package append the USE fag (IUSE="${IUSE}
16 > ${JAVA_PKG_OPT_USE}") instead of replacing it?
17
18 No, portage itself takes care to put eclass-defined and ebuild-defined
19 IUSE together.
20
21 > And in order to solve the conflict that may introduce when several
22 > eclasses overwrite the pre* functions, shouldn't you EXPORT_FUNCTIONS
23 > them?
24
25 No, EXPORT_FUNCTIONS is for exporting the phases itself, not phase
26 hooks. Both seem to solve conflict in a way that the later
27 defined/inherited wins, so in the end you get one phase function and one
28 phase hook.
29
30 --
31 Vlastimil Babka (Caster)
32 Gentoo/Java
33 --
34 gentoo-java@g.o mailing list

Replies

Subject Author
Re: [gentoo-java] generation-2 java eclass Alon Bar-Lev <alon.barlev@×××××.com>