Path: csiph.com!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From: Markus Koschany <apo@debian.org>
Newsgroups: linux.debian.maint.java
Subject: Re: gradle reboot
Date: Tue, 26 Nov 2024 14:20:01 +0100
Message-ID: <JN3DX-bLiV-1@gated-at.bofh.it>
References: <JJqpr-9klD-5@gated-at.bofh.it>
Old-Return-Path: <apo@debian.org>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-QTdjW3fTNTXtce9p18i8"
MIME-Version: 1.0
Approved: robomod@news.nic.it
Lines: 79
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:12834


--=-QTdjW3fTNTXtce9p18i8
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Julien,

First of all, thank you for working on Gradle. I have been working on it in=
 the
past and together with Emmanuel we tried different approaches. Currently I
can't spend more time on it, but I have uploaded my last attempt to

https://salsa.debian.org/java-team/gradle-apo

perhaps this might be helpful for someone.

I discarded the idea to upgrade Gradle to 6.x or even newer releases becaus=
e
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 betwe=
en
upgrading existing Debian packages, then fixing broken reverse-dependencies=
,
and then moving on to build Gradle offline. And for me those iterations nev=
er
seemed to end.

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 releas=
e of
4.6 and installed it to /opt/gradle/gradle-4.6. I managed to successfully b=
uild
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.=20

I believe all remaining issues are related to our Kotlin version in Debian,=
 the
kotlin-gradle plugin and the gradle-kotlin-dsl-extensions and a few patches=
 to
tie them all together. Upstream used a different version of Kotlin to build=
 4.6
and that might be one of the reasons for the broken Debian package. I wish =
you
all the best and try to follow up as soon as time permits.

Regards,

Markus



--=-QTdjW3fTNTXtce9p18i8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----

iQKTBAABCgB9FiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmdFyIBfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQACgkQ2a0UuVE7
UeSsMhAAm1TziJBYDATV1GM3QwnkoG9OIiN+XtPUypW63A5ZxPUIFSoEOQ9yYD8Y
L3PVGdwja/l1dqNgRFcwOtqBgdS1Vsx7jPyghNdCPl9NrH18ivllGe6Lli7QOXpS
hrKQQ/866/zfRylz/4HP1Hs0WilgEVCXy/nGo3Q8z3gxVjWvs+IIL5xSqISk13WE
znQDDnremdKmmxWmQGN3dC/aNy//fXgCxMYGhaAZcyz6gc7aHBnfth4M6U0cSYzn
QwazV10/jNtAyszNVqWAvC2+m58Bt6kXLuUYyo2GW1aTl/wnBmUASWF7ZZFu1zQN
UItce1kyHHyjTNnbkpR2vn/I6IqjXAXgeJEjOrRF97fYtbQgbdLle/zSFgUU3ItG
6DEHJySHlcYFDx7wkpM1X7DKIzJohR72llE/l/LkyMitfICPUPdZVEbAYdkwh/YD
jeoOXKbCIVYj9QpgI33mkiToaHrgO2uBJSXAw0a2KKZIVXwZA2N37dNrx9IsitaM
ZuUbsfA478UnXM1aNloKMdeHGmMRhUIVRsflDaLVmO30NE5W3kDjDKIM5yr17wpq
pZez6qUBA/fNzsc65JYVti0LTql59x1Xb9i72E3o6LLPvyC23ALKJdg2ZkXfiCkw
g54c/93vi4Vm5bB3uev0HSXMkYP9fRXEi6Wv34kudmUoOXOr2sk=
=dBid
-----END PGP SIGNATURE-----

--=-QTdjW3fTNTXtce9p18i8--