Bug 3634

Summary:	USE flag for Jikes?
Product:	Gentoo Linux	Reporter:	Maik Schreiber <blizzy-keyword-gentoo_bugs2.a8a736>
Component:	[OLD] Unspecified	Assignee:	Karl Trygve Kalleberg (RETIRED) <karltk>
Status:	RESOLVED FIXED
Severity:	enhancement
Priority:	High
Version:	1.2
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---

Description Maik Schreiber 2002-06-11 12:18:03 UTC

Can we have a USE=jikes flag for dev-java/jikes? This way you don't have to
compile using the old and slow original javac, which is especially worse for
large packages like app-editors/jedit, for example.

Comment 1 Karl Trygve Kalleberg (RETIRED) gentoo-dev

2002-06-24 16:24:07 UTC

I am not sure. What I suggest is that all Java packages should use Jikes if it
is installed, of not, default back on javac.

Some packages will not compile with Jikes, and some packages will not compile
without it, but for all others, it would be nice to support both compilers, with
Jikes being the preferred one.

If this sounds okay, I'll add it to the java ebuild guidelines. If not, reopen
the bug with your protests :P

It will of course take a while before all the java ebuilds will conform to this
policy.

Comment 2 Maik Schreiber 2002-06-24 17:18:32 UTC

The problem is, how to test for Jikes? Of course, a simple "if [ -x
/usr/bin/jikes ]" would work, but I don't think this is good practice.

A real USE flag would be much better, despite the fact that we already have
DEPEND (compile-time dependencies) and RDEPEND (run-time dependencies). (As far
as I know, Portage doesn't support those correctly right now, merging DEPEND
into RDEPEND, but I really do think we should pretend it did.)