From: Vlastimil Babka <caster@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] generation-2 java eclass
Date: Thu, 21 Sep 2006 19:58:28 +0200 [thread overview]
Message-ID: <4512D2C4.4000908@gentoo.org> (raw)
In-Reply-To: <9e0cf0bf0609202205l3b79649y93e87f84ab3cdc79@mail.gmail.com>
Alon Bar-Lev wrote:
> Looking at bug#146647, why did you remove the java from the IUSE? I
Because the eclass provides it already. Ebuild doesn't need to.
> don't think it is a clean to require programmer to define the
> JAVA_PKG_OPT_USE before the inherit... Or you need to add a BIG FAT
> WARNING at the eclass documentation/description.
You're getting it wrong. JAVA_PKG_OPT_USE is just a name for the flag
that triggers java support. You need to specify it before inherit line
if you want the flag to be called differently than "java" (the default).
Not sure if any ebuild ever overrided that, it's just the possibility.
> And shouldn't the package append the USE fag (IUSE="${IUSE}
> ${JAVA_PKG_OPT_USE}") instead of replacing it?
No, portage itself takes care to put eclass-defined and ebuild-defined
IUSE together.
> And in order to solve the conflict that may introduce when several
> eclasses overwrite the pre* functions, shouldn't you EXPORT_FUNCTIONS
> them?
No, EXPORT_FUNCTIONS is for exporting the phases itself, not phase
hooks. Both seem to solve conflict in a way that the later
defined/inherited wins, so in the end you get one phase function and one
phase hook.
--
Vlastimil Babka (Caster)
Gentoo/Java
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-09-21 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 17:07 [gentoo-java] generation-2 java eclass Alon Bar-Lev
2006-09-16 23:40 ` Vlastimil Babka
2006-09-20 10:07 ` Alon Bar-Lev
2006-09-20 20:31 ` Vlastimil Babka
2006-09-20 22:41 ` Vlastimil Babka
2006-09-21 5:05 ` Alon Bar-Lev
2006-09-21 15:42 ` William L. Thomson Jr.
2006-09-21 16:55 ` Alon Bar-Lev
[not found] ` <4512C781.7000709@serent.com>
2006-09-21 17:24 ` Kurt Guenther
2006-09-21 17:34 ` William L. Thomson Jr.
2006-09-21 17:58 ` Vlastimil Babka [this message]
2006-09-21 18:04 ` Alon Bar-Lev
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=4512D2C4.4000908@gentoo.org \
--to=caster@gentoo.org \
--cc=gentoo-java@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