Obviously count us in, Fabio :-) ----- Original Message ----- > From: "Fabio Valentini" <decathorpe@xxxxxxxxx> > To: "Development discussions related to Fedora" <devel@xxxxxxxxxxxxxxxxxxxxxxx> > Sent: Tuesday, May 12, 2020 6:39:04 AM > Subject: Re: Re-Launching the Java SIG > > On Tue, May 12, 2020 at 12:34 PM Ty Young <youngty1997@xxxxxxxxx> wrote: > > Right, I figured it was some Fedora policy and not up to you. I suppose > > I should have been more clear there. Sorry for any confusion, it was > > aimed at the Fedora project as a whole as this is a Fedora issue. > > I am aware that Arch is just packaging up the binary release artifacts > published by the gradle project. > But that's just never going to fly for fedora. > > Arch is also the only distro I looked at that does this, everybody > else (at least debian, ubuntu, OpenSUSE) is stuck at an ancient > version, if gradle is available at all. > > > FWIW, I can compile 6.4 just fine on Arch Linux using the Github source > > code via: > > > > > > ./gradlew allZip > > Now try doing that offline and without using the pre-built > gradle/wrapper/gradle-wrapper.jar :) > You'll be surprised how much junk the build process still needs to download. Do we need a two-step bootstrap process? A first (offline) step where we run gradle-wrapper and fetch all the resources, put all online dependencies into a SRPM/lookaside cache and "finish" the bootstrap build in Koji (giving us a bootstrapped version which works) and then replacing _all_ assets with versions built using the bootstrapped gradle and finally rebuilding gradle? It'd be hell to set up the first time (two .specs?) and hell to make sure we get every package at the right version. But theoretically possible? :-) But it might allow us to skip incremental bootstrap from a really old gradle version and might even get us a process which works for future bootstraps. - Alex > > Fabio > > > > > > > Felix > > > _______________________________________________ > > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > > > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > > Fedora Code of Conduct: > > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > > List Archives: > > > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > > _______________________________________________ > > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > Fedora Code of Conduct: > > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
