Hi, Am Mittwoch, dem 27.11.2024 um 09:16 +0100 schrieb sre4e...@free.fr: > [...] > 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...
I remember that upstream confirmed they only use nightly builds to build gradle and don't promise that any later version may be able to build an older version. The advantage of my 4.6 package was that I managed to update all our patches and could use existing Debian packages at that time. I imagine one year later it is still less work to update those patches again, if someone wants to go the 4.6 route. I had the idea to use the bundled 4.6 Kotlin binaries in a next step. If that had worked, at least it would have confirmed we just need to focus on upgrading Debian's Kotlin package while everything else was already there. You're right, 4.6 would still be a very old release. I could imagine that upgrading from 4.6 to 4.8 and 4.10 is faster though, and we could skip a few releases later. Jumping directly to gradle 8 would be perfect of course. Cheers, Markus
signature.asc
Description: This is a digitally signed message part
