From: Vlastimil Babka <caster@gentoo.org>
To: gentoo-java <gentoo-java@lists.gentoo.org>
Subject: Re: [gentoo-java] plz review some ebuilds
Date: Mon, 04 May 2009 20:33:11 +0200 [thread overview]
Message-ID: <49FF34E7.8000404@gentoo.org> (raw)
In-Reply-To: <200905041934.55112.fetka@arge.at>
Mario Fetka wrote:
> Hallo Gentoo Java Team,
>
> can someone plz review some java related ebuilds[1]
>
> dev-java/isrt
> dev-java/isnativec
> dev-java/isfreetype
> dev-java/iscwt
> dev-java/jPod
> dev-java/jPodRenderer
> dev-java/jbig2
> app-text/pdfsam
Hi, just a quick... I'll talk about iscwt-5.0.20081218.ebuild but most
should apply to others too.
depends on swt:3.4 using a slot dep without EAPI=1 (or later) which
should not even work. In general, use EAPI=2 and specify slot deps for
everything dev-java except jdk/jre (even explicitly :0 as it eases
future upgrades). With EAPI=2 you can call 'default' instead of 'unpack
$A; cd $S;'. The mkdir and cp calls should have appen '|| die'
Move doc from IUSE to JAVA_PKG_IUSE.
The creation of build.properties is tedious, overriding the classpath
(see below) should be easier.
What is the ${antflags} doing in src_compile? Should not be there. Also
there should be just one eant call and using $(use_doc) as parameter
will add 'javadoc' based on the flag.
Also the whole src_compile (and the build.properties stuff) could be
replaced with this:
JAVA_ANT_REWRITE_CLASSPATH="true"
EANT_GENTOO_CLASSPATH="isnativec,isrt,jna"
Not tested, so some details might vary. Hope it helps.
Caster
> before i will put them into bugzilla
>
> thx in av
> Mario
>
> [1]http://tinyurl.com/co97l6
> http://tinyurl.com/dg3vhv
>
>
next prev parent reply other threads:[~2009-05-04 18:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 17:34 [gentoo-java] plz review some ebuilds Mario Fetka
2009-05-04 18:33 ` Vlastimil Babka [this message]
2009-05-04 18:50 ` Mario Fetka
2009-05-04 22:31 ` Mario Fetka
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=49FF34E7.8000404@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