Hi, I've created an ebuild for dev-java/rome 0.9 (java library/tools for generating, parsing and converting Atom and RSS feeds) It's the first ebuild I've ever made, so please let me know if I made some horrendous mistakes :-) The ebuild does contain a src_test block, but one of the unit tests fails due to a small error/omission in Rome's build.xml, so it's commented out (reported to the Rome bug list, issue 55) Also note that the SRC_URI contains asterisks (*), so there might be a warning ("wildcards not supported in HTTP") when emerge starts to download the source. Best regards, Bart
Created attachment 104944 [details] dev-java/rome-0.9.ebuild
I had rome-0.8 in an overlay, just updated it to 0.9. See https://overlays.gentoo.org/svn/proj/java/migrated-java-experimental-overlay/dev-java/rome
Some notes on your ebuild: * ${P} is equivalent to ${PN}-${PV}, so use that whenever possible. * jdom is slotted funkily, so make sure to depend on a more specific atom, ie ~dev-java/jdom-1.0 * S defaults to ${WORKDIR}/${P}, so it's not necessary to specify it in this case. * java-pkg-2 provides a default src_compile, which would cover this particular case * maybe the broken test should be disabled/deleted, instead of disabling them all? * don't install versioned jars. use java-pkg_newjar to rename it to just ${PN}.
ok, thanks for the feedback. I'll take a look at the java overlay wiki
I improved the ebuild and moved it to tree.
