hello Emmanuel and debian-java, Emmanuel Bourg <ebo...@apache.org> writes: > Le 06/10/2019 à 19:02, shirish शिरीष a écrit : > >> I had read Saif blog posts and it seems some of the parts are stuck in >> the NEW queue. Does anybody have any idea or have people prodded the >> ftp-masters to see what is holding up the introduction to the archive >> ? > > The remaining dependencies prepared by Saif are all in the NEW queue > now. But that isn't the limiting factor, there are issues left with the > kotlin package. It does build, once installed the REPL works fine, but > it fails to build itself. The compilation breaks with a nasty exception. > > The other issue is the kotlin-boostrap package, it contains prebuilt > binaries that we have to build from sources (at least the kotlinx > artifacts).
Would it help if I would package one (or more) of the kotlinx libraries? The question is: which one? https://salsa.debian.org/m36-guest/kotlin-bootstrap/-/tree/master/kotlinx -> contains kotlinx-coroutines-core, kotlinx-metadata-jvm and kotlinx-serialization-runtime jars. but none of these is still active: https://github.com/Kotlin/ -> so would it make sense to look at kotlinx.coroutines (contains kotlinx-coroutines-core module) or kotlinx.serialization (contains a runtime module) now? (kotlinx.coroutines has 10 dependencies, so I wonder whether it is feasible for debian-java to package all kotlin libraries where each has a number of sub-dependencies?) Cheers and Best Regards, -- Felix Natter debian/rules!
