Path: csiph.com!weretis.net!feeder8.news.weretis.net!fu-berlin.de!news.servidellagleba.it!bofh.it!news.nic.it!robomod From: sre4ever@free.fr Newsgroups: linux.debian.maint.java Subject: Re: gradle reboot Date: Wed, 27 Nov 2024 09:20:02 +0100 Message-ID: References: X-Original-To: debian-java@lists.debian.org X-Mailbox-Line: From debian-java-request@lists.debian.org Wed Nov 27 08:17:05 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.199 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 MIME-Version: 1.0 User-Agent: Webmail Free/1.6.9 X-Sender: sre4ever@free.fr Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Mailing-List: archive/latest/23542 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/dd585d50935c251c41ee962106022340@free.fr Approved: robomod@news.nic.it Lines: 50 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 27 Nov 2024 09:16:51 +0100 X-Original-Message-ID: X-Original-References: <78a8c1b6-c034-7e27-a0fa-9558adfcdfa9@free.fr> <1f8b8ba84612d8e1025cd32ef04c229936fdd117.camel@debian.org> Xref: csiph.com linux.debian.maint.java:12835 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