Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: libvirt-java: Java bindings for the libvirt library https://bugzilla.redhat.com/show_bug.cgi?id=453119 ------- Additional Comments From veillard@xxxxxxxxxx 2008-07-01 10:21 EST ------- Okay, finding the right include paths for JNI stuff is fairly messy, and well gcj-devel has a bug plugging them by default in gcc include path (fun see #453572). I think I have ironed out the problems, regenerated a new 0.1.1 release SRPMS: ftp://libvirt.org/libvirt/java/libvirt-java-0.1.0-1.fc9.src.rpm spec: ftp://libvirt.org/libvirt/java/libvirt-java.spec wei:~/libvirt-java -> rpmlint /u/veillard/rpms/SRPMS/libvirt-java-0.1.1-1.fc9.src.rpm libvirt-java.src: E: unknown-key GPG#de95bc1f libvirt-java.src: W: strange-permission libvirt-java.spec 0600 1 packages and 0 specfiles checked; 1 errors, 1 warnings. wei:~/libvirt-java -> I think if one ignore the fact that rpmlint doesn't know my PGP key this looks decent. For the spec file I used the following: %define java java and Requires: %{java} >= 1.5.0 BuildRequires: %{java}-devel >= 1.5.0 because some users may want to define more precisely which java environment they want for development. Ideally this should remain that flexible (the src RPM rebuit even on a RHEL4 with Java SDK in /usr/lib/jvm/java-1.5.0-ibm-1.5.0.7) I hope it's okay now, Daniel -- 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, or are watching someone who is. _______________________________________________ Fedora-package-review mailing list Fedora-package-review@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/fedora-package-review