Re: gradle reboot
Hi Markus,
Thanks for the link to your repo, I will take a look.
Le 2024-11-26 14:09, Markus Koschany a écrit :
I discarded the idea to upgrade Gradle to 6.x or even newer releases
because
the main problem with Gradle for Debian is the complex interaction
between its
(build)-dependencies. Since we only support one version of a library in
general, you will quickly reach a point where you are stuck in a loop
between
upgrading existing Debian packages, then fixing broken
reverse-dependencies,
and then moving on to build Gradle offline. And for me those iterations
never
seemed to end.
Both Gradle and Kotlin are moving targets indeed, and they were moving
even faster around these releases according to their respective
histories, which probably explains why you (and nobody else as a fact)
weren't able to catch up: it might well have been simply impossible at
that stage.
My last idea was to only make a small step forward and upgrade Gradle
to 4.6,
the first version that uses Kotlin. I downloaded the official binary
release of
4.6 and installed it to /opt/gradle/gradle-4.6. I managed to
successfully build
gradle 4.6 offline with Debian packages but only with the official
binary
release. If I replace this one with the resulting Debian package and
try to
rebuild Gradle, the build fails.
I would not follow that path today for Gradle unless working on a
theoretical bootstrap. That would still be a difficult work, maybe even
more difficult than the current releases, and the result would still be
a severely outdated Gradle, just a little bit less outdated, and with
still a lot of work ahead to bring it to current releases.
But I wouldn't rule out a similar path for Kotlin yet as we may well
lack alternatives for that one...
Cheers,
--
Julien Plissonneau Duquène
Reply to: