Red Hat Bugzilla – Full Text Bug Listing
|Summary:||Review Request: classpath-0.92 - Essential Libraries for Java|
|Product:||[Fedora] Fedora||Reporter:||Paul F. Johnson <paul>|
|Component:||Package Review||Assignee:||Nobody's working on this, feel free to take it <nobody>|
|Status:||CLOSED NOTABUG||QA Contact:||Fedora Package Reviews List <fedora-package-review>|
|Version:||rawhide||CC:||fitzsim, fnasser, green|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2006-09-27 17:20:24 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Paul F. Johnson 2006-09-19 02:06:57 EDT
Spec URL: www.knox.net.nz/~nodoid/classpath-0.92-1jpp SRPM URL: www.knox.net.nz/~nodoid/classpath.spec Description: GNU Classpath, Essential Libraries for Java, is a GNU project to create free core class libraries for use with virtual machines and compilers for the java programming language. Please note, this is my first ever attempt to package a java product, so be gentle with me. The spec file contains two files in the normal %files section with a hard coded /usr/lib. When I compiled it (outside of mock), on my x86_64 box, these two files were created. I have no idea if this is correct or not.
Comment 1 Paul F. Johnson 2006-09-19 17:33:29 EDT
Spec URL: www.knox.net.nz/~nodoid/classpath-0.92-2jpp SRPM URL: www.knox.net.nz/~nodoid/classpath.spec A couple of rpmlint fixes. I'll remove the jpp suffix next spin
Comment 2 Ville Skyttä 2006-09-19 18:00:37 EDT
Parts of GNU Classpath are already being shipped in Core, eg. gnu-crypto. Maybe it would be beneficial to try and combine efforts somehow? Are there any potential issues with gcj if the same but possibly subtly different versions of the same class (eg. from gnu-crypto and classpath) end up in the same classloader?
Comment 3 Paul F. Johnson 2006-09-19 18:06:53 EDT
I would imagine that if classpath is newer than the bits already in core, then they will be used in preference to the existing ones. As to what damage that may cause, I have no idea. I do know though that gcj is not up to the job to compile ikvm or limewire... I'm all for co-operating as well :-)
Comment 4 Thomas Fitzsimmons 2006-09-20 12:14:16 EDT
(In reply to comment #3) > As to what damage that may cause, I have no idea. I do know though that gcj is > not up to the job to compile ikvm or limewire... If your goal is to package LimeWire for Fedora Core, then the easiest way is likely to fix whatever GCJ problems are preventing you from building it. Limewire >= 4.13 requires Java 1.5 so it probably won't be buildable until FC-7, but in the meantime we should package 4.12: svn co http://limewire.org/svn/limewire/branches/bugfix-4-12-branch limewire cd limewire/core ant cd ../gui ant That builds fine on my i686 Rawhide test machine, using the system-installed ecj/libgcj.
Comment 5 Fernando Nasser 2006-09-20 21:25:19 EDT
I have a limewire-3.5.6-3jpp RPM that I could try and upgrade to 4.12
Comment 6 Anthony Green 2006-09-26 09:41:38 EDT
I don't think packaging GNU Classpath as an independent package is a good idea. We discussed this a little on the fedora-devel-java-list. Your two reasons for wanting this packaged were: 1. To solve the ikvm-bundles-classpath-binaries problem 2. To build limewire We don't need this for , as per comment #4. For the ikvm problem, please just add the appropriate GNU Classpath source release as a SOURCE to the ikvm spec file, and build it as part of the ikvm package build. We're trying to keep JRE packaging consistent and, while I realize that IKVM is different in many ways, installing a stand-alone Classpath jar file is sure to lead to problems down the road.
Comment 7 Paul F. Johnson 2006-09-27 17:20:24 EDT
Fair enough. I'll withdraw the package from review. Thanks for the comments :-)