Path: csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From: Phil Morrell <debian@emorrp1.name>
Newsgroups: linux.debian.maint.java
Subject: Re: Mindustry packaging
Date: Thu, 10 Dec 2020 01:40:01 +0100
Message-ID: <Bki9X-15V-1@gated-at.bofh.it>
References: <Bka2K-4wG-7@gated-at.bofh.it> <BkdtD-6GH-11@gated-at.bofh.it> <BkdDj-6K6-7@gated-at.bofh.it>
Old-Return-Path: <debian@emorrp1.name>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx"
Content-Disposition: inline
User-Agent: Mutt/1.10.1 (2018-07-13)
Approved: robomod@news.nic.it
Lines: 55
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:11991


--dDRMvlgZJXvWKvBx
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Stephen,

I'm the one who did the initial triage to discover the surprising kotlin
requirement, but I'll gladly collaborate once that's available. I'm
thoroughly enjoying the new v6 campaign in co-op with some friends, so
keen to be able to play it via debian rather than a .jar download with
e.g. embedded Discord server listings.

On Wed, Dec 09, 2020 at 02:41:57PM -0500, Stephen Paul Weber wrote:
> > Dependencies can not be downloaded during the build.
>=20
> Yes, of course, that is the problem described in my OP :)

As you said, many Java projects have switched to gradle so thankfully
the hard work to integrate it with Debian has already been done. The
upstream bundled ./gradlew will be completely ignored and that bit is as
simple as adding gradle-debian-helper to Build-Depends and
--buildsystem=3Dgradle to debian/rules.

https://sources.debian.org/src/gradle-debian-helper/2.1/README.txt/

> > And the bug lists the first blocker which then lists the other blocker
> > and the last blocker is kotlin (or shall I say the first blocker).
>=20
> I'm having trouble following the breadcrumbs to see where kotlin becomes =
the
> blocker.  I assume because one of the dependencies is written it kotlin?

In the summary at the top, you can follow the link in "Fix blocked by"
(and then "Fix blocked by" again, etc.). As for why each dependency is a
blocker, I hope my initial message in each RFP makes that clear. The
current state of kotlin packaging is really promising, with (hopefully)
just normal java packaging issues left.

Help needed! "Make sure you have kotlin-reflect.jar in the classpath"
https://salsa.debian.org/android-tools-team/admin/-/issues/34

--dDRMvlgZJXvWKvBx
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSBP39/Unco6Ai78+TbymUJHySObAUCX9FtiwAKCRDbymUJHySO
bEMOAP9MvLjvlkXwZpH2VVW8StReNV1o3Q29Swmokq56ctqY7AEAjLQ3TAjNPSlf
A2O5xXj6RbfKC272IQ57CpPb8xFaaws=
=WuB9
-----END PGP SIGNATURE-----

--dDRMvlgZJXvWKvBx--