From: Vlastimil Babka <caster@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] RFC: Default src_compile for java-pkg-2.eclass
Date: Mon, 11 Dec 2006 11:59:23 +0100 [thread overview]
Message-ID: <457D3A0B.5090301@gentoo.org> (raw)
In-Reply-To: <457CE72F.7050906@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Joshua Nichols wrote:
> How many packages would benefit from this?
>
> Some ways to improve it... maybe have two variables, ie
> EANT_BUILD_TARGET, EANT_DOC_TARGET, which could be set and respected by
> src_compile, ie:
>
> java-pkg-2_src_compile() {
> local antflags="${EANT_BUILD_TARGET:=jar}"
> hasq doc ${IUSE} && antflags="${antflags} $(use_doc
> ${EANT_DOC_TARGET})"
> eant ${antflags}
> }
>
> By adding that, I think more ebuilds would be able to take advantage of it.
>
I wonder if ebuild using those variables would be more typing than
ebuild with own src_compile() :) but not a bad idea anyway.
> One other thing... should definately check for the existence of a
> build.xml... and additionally, could have a variable to specify where
> the build file lives.
Yeah check is needed, otherwise you'll be trying to compile current -bin
packages without src_compile() in ebuild...
Not sure if any ebuild would use the variable, but why not...
- --
Vlastimil Babka (Caster)
Gentoo/Java
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFfToKtbrAj05h3oQRAjklAJ95WFKtG/l9BXPwA3CvFwbprYXEVACaArRY
nVl3h/IW+wfgYx0hyvUWvqc=
=d2lM
-----END PGP SIGNATURE-----
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2006-12-11 11:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 12:19 [gentoo-java] RFC: Default src_compile for java-pkg-2.eclass Petteri Räty
2006-12-11 5:05 ` Joshua Nichols
2006-12-11 10:59 ` Vlastimil Babka [this message]
2006-12-11 15:04 ` Joshua Nichols
2006-12-17 16:44 ` Petteri Räty
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=457D3A0B.5090301@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