Marián Konček wrote:
> I had the same question and I don't exactly remember the most important
> reason, but it was something like there were large differences between
> versions which made the builds more difficult. Now I see it also uses
> Kotlin, maybe that is also a reason. Upstream projects tend to just
> bundle their own Gradle with them for building.
Bootstrapping is one issue. As you noticed, Gradle now depends on Kotlin,
which in turn requires Gradle to build, a circular dependency.
Another is that, as was already mentioned by Fabio Valentini, neither Gradle
projects nor Gradle itself are designed to be built without Internet access,
which is a requirement for Fedora.
Upstream's (Google's) idea of bootstrapping is that Gradle just downloads
prebuilt JARs of all the dependencies from the Internet at build time, which
violates both the "no Internet access" and the "no binary blobs" rule in
Fedora. The first of which is a requirement for the package to build at all
in Koji, the second a MUST-level Packaging Guideline.
Kevin Kofler
--
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
