Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=508836 --- Comment #7 from Jason Tibbitts <tibbs@xxxxxxxxxxx> 2009-07-01 17:55:15 EDT --- (In reply to comment #6) > What I am not sure of is if someone does a build with the gcj stuff installed, > but not openjdk stuff, can they get arch dependent output? No. Your package would have to call aot-compile-rpm. I asked the java folks and it seems that the current state of affairs is that if you don't do the aot stuff as outlined in the GCJGuidelines document, at least ARM and PPC architectures will run the code very slowly. > I'll also do some more reading about javadoc. I thought this was pretty much > required, but it really doesn't make much sense for stand alone programs. It only makes sense if the upstream code actually has javadoc content; yours doesn't seem to. (Or at least it isn't generated by the build process.) And I agree, I don't see what point javadoc would have for an standalone application. End-user documentation would be better, but probably wouldn't be packaged separately unless it was very large. -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review