I talked to jlaska about this, but his response was: "I maintain a gwt package in a private repo since it's a %buildrequires for autotest. However, I've given up on attempting to package the world of java just since it's way beyond my skill level. so in it's current state, it contains a slew of bundled JARs that would never be accepted as an official Fedora package."
so my original question about how to handle the guava<->gwt dependency loop still stands. --Andy On Thu, Aug 4, 2011 at 1:32 PM, Andy Grimm <agr...@gmail.com> wrote: > I did see a spec file at http://jlaska.fedorapeople.org/ , but it didn't > look functional. That page is much more informative, thanks! > > > On Thu, Aug 4, 2011 at 11:06 AM, Johannes Lips < > johannes.l...@googlemail.com> wrote: > >> Hi, >> are you aware of the effort James Laska already put into this? >> http://fedoraproject.org/wiki/User:Jlaska/autoqa_package_dependencies >> If you already have talked to him, forget about this e-mail ;-) >> >> -Johannes >> >> On Thu, Aug 4, 2011 at 4:43 PM, Andy Grimm <agr...@gmail.com> wrote: >> >>> Hi, everyone. I'm looking into packaging gwt (Google Web Toolkit) 2.3 >>> and guava r09. In this new version (unlike Fedora's current version r05), >>> the full guava build requires gwt. gwt, of course, requires guava to >>> build. So, I'm looking at doing the following: >>> >>> * build guava without guava-gwt (so that gwt is not required for the >>> build) >>> * build gwt (which has a whole pile of other problems, but that's for >>> another day) >>> * build guava-gwt as a completely separate package, using essentially the >>> same upstream source as the guava package >>> >>> Is this the accepted way to go about this? or should I actually be using >>> a "bootstrap" guava package to build gwt, and then rebuild guava with a >>> guava-gwt subpackage (thus leaving a build dependency loop). >>> >>> --Andy >>> >>> -- >>> devel mailing list >>> devel@lists.fedoraproject.org >>> https://admin.fedoraproject.org/mailman/listinfo/devel >>> >> >> >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel >> > >
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
