Path: csiph.com!weretis.net!feeder8.news.weretis.net!fu-berlin.de!bofh.it!news.nic.it!robomod
From: Markus Koschany <apo@debian.org>
Newsgroups: linux.debian.maint.java
Subject: Re: gradle reboot
Date: Sat, 30 Nov 2024 09:50:01 +0100
Message-ID: <JOrkR-cIPA-19@gated-at.bofh.it>
References: <JJqpr-9klD-5@gated-at.bofh.it> <JN3DX-bLiV-1@gated-at.bofh.it> <JNlrc-bWRe-3@gated-at.bofh.it>
Old-Return-Path: <apo@debian.org>
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="=-LVP05QdA+yQ90qr9m8QT"
MIME-Version: 1.0
Approved: robomod@news.nic.it
Lines: 71
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:12844


--=-LVP05QdA+yQ90qr9m8QT
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

Am Mittwoch, dem 27.11.2024 um 09:16 +0100 schrieb sre4ever@free.fr:
> [...]
> I would not follow that path today for Gradle unless working on a=20
> theoretical bootstrap. That would still be a difficult work, maybe even=
=20
> more difficult than the current releases, and the result would still be=
=20
> a severely outdated Gradle, just a little bit less outdated, and with=20
> still a lot of work ahead to bring it to current releases.
>=20
> But I wouldn't rule out a similar path for Kotlin yet as we may well=20
> lack alternatives for that one...

I remember that upstream confirmed they only use nightly builds to build gr=
adle
and don't promise that any later version may be able to build an older vers=
ion.
The advantage of my 4.6 package was that I managed to update all our patche=
s
and could use existing Debian packages at that time. I imagine one year lat=
er
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 th=
at
had worked, at least it would have confirmed we just need to focus on upgra=
ding
Debian's Kotlin package while everything else was already there. You're rig=
ht,
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

--=-LVP05QdA+yQ90qr9m8QT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----

iQKTBAABCgB9FiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmdKz31fFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQACgkQ2a0UuVE7
UeTcBQ//WO6hgOmviuSGxlVV6HD6aXquTOtmgf1e7vP7YS54xH1XTrg2yUWJ70Ly
KhEDaeDx/6/hJ3eKkrvRGC8bMtsW4t6PJ4APtT9Y3AGiKJwlX7+0KAu39plTtMt6
PDfHk60+QRAb3Rcd3IuoZYaSh1r7eyI5N2Ta/RY2MHUO1boXbAO6dteN/Bhkl7yC
e39c03G0o+IsXzmTv7ThHQXdZ39rFKXAALMn8SPtyZafolXy53iOtzH/hcOFL7rT
2Zi2dJhKm6aslDw4QwVl0Pbv2d2WlKkk9I/Y+VidhfohtZFiY3quHJALCcx4+jy2
73QSdN5gSUHvy1mSuOc2WaYCnqUQYjO04ytMq1iWmYHlNOJGulgFfqnCIthYvmOj
NuK50+W9KVUIMHOHV2bnw8CnR5nZnp+8NK9KJhKYUpXkn6Q5Ff/qtdaYfcl/zLBy
BsmQqhzilkBn2qB4PoMALRGNfYuGIoCSGVXv5TxZ/2KzZqoQwCsB9m6P22BmQIXZ
4OM8fDwC94mgZwk7+mijrvrXb+Qvy/grVFt032vNhNj+dvN5kKk74bHCG+Qrghc7
PBUe3/gtp2dA86Os/c3oDx1gVLSCrY5du27Lx/igJh62JrQT5eSklWJB59TZbtNY
CuK6iW2hkv/6RnBDYnSMZW7Z2TNn63RCV+pTAoZ44gGNDCy92eY=
=KVYw
-----END PGP SIGNATURE-----

--=-LVP05QdA+yQ90qr9m8QT--