Hi,
isn't nowadays openjdk-1.6.0-java-devel supposed to be the Java compiler we use always?
I just noticed that the java-devel that is supposed to be used in spec files pulls in
java-1.5.0-gcj-devel-1.5.0.0-28.fc11.x86_64
which made my jaxodraw compilation fail (gcj isn't supported). Shouldn't the provides: java-devel be removed from java-1.5.0-gcj-devel since this causes problems?
On 06/06/2009 06:17 AM, Jussi Lehtola wrote:
Hi,
isn't nowadays openjdk-1.6.0-java-devel supposed to be the Java compiler we use always?
I just noticed that the java-devel that is supposed to be used in spec files pulls in
java-1.5.0-gcj-devel-1.5.0.0-28.fc11.x86_64
which made my jaxodraw compilation fail (gcj isn't supported). Shouldn't the provides: java-devel be removed from java-1.5.0-gcj-devel since this causes problems?
IMO, if your app can only use openjdk, then explictly BuildRequires: java-devel-openjdk
-- Rex
On Sat, 2009-06-06 at 10:52 -0500, Rex Dieter wrote:
On 06/06/2009 06:17 AM, Jussi Lehtola wrote:
Hi,
isn't nowadays openjdk-1.6.0-java-devel supposed to be the Java compiler we use always?
I just noticed that the java-devel that is supposed to be used in spec files pulls in
java-1.5.0-gcj-devel-1.5.0.0-28.fc11.x86_64
which made my jaxodraw compilation fail (gcj isn't supported). Shouldn't the provides: java-devel be removed from java-1.5.0-gcj-devel since this causes problems?
IMO, if your app can only use openjdk, then explictly BuildRequires: java-devel-openjdk
Yes, that's what I am using now (BR: java-1.6.0-openjdk-devel, R: java-1.6.0-openjdk), I was just wondering if the provides in gcj is a packaging bug..
* Jussi Lehtola jussilehtola@fedoraproject.org [2009-06-06 12:34]:
Yes, that's what I am using now (BR: java-1.6.0-openjdk-devel, R: java-1.6.0-openjdk), I was just wondering if the provides in gcj is a packaging bug..
It's not really a bug. If you want to be JVM-agnostic, use:
java-devel >= 1:1.6.0
Andrew
packaging@lists.fedoraproject.org