Hi Benda, Thanks for the reference to Java Packing policy since I haven't read it before.
I also forget to mention maven build system in last email, but for now I'm only focused on scala and sbt. On 4/19/20 5:31 AM, Benda Xu wrote: > That's a good idea. What's your plan to realize the eclasses? Taking into account the network sandbox requirement, sbt.eclass needs to download all dependencies with some approach like EGO_SUM implementation in go-module.eclass[1]. Looking in more detail to scala ebuild[2] as a reference, as a quick brainstorm, I think that could be defined: sbt.eclass - ESBTV = <sbt version to be set in ebuild> This would set the DEPEND for sbt and set the necessary steps to java-pkg-2_pkg_setup, check-reqs_pkg_setup, check-reqs_pkg_pretend, java-pkg_getjars and do the substitution of SBTV in build.properties if required - envset parameters (src_prepare): definition of parameters to set necessary environment for sbt wrapper that use defined ESBTV - ESBT_SUM = <list of project dependencies to be loaded within source unpack> - esbt_compile, esbt_run, esbt_package functions: to run sbt using envset wrapper in compile, test and install as necessary scala.eclass - ESCALAV = <set scala version> - ... to be defined as required Best, Samuel [1] https://devmanual.gentoo.org/eclass-reference/go-module.eclass/index.html [2] https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-lang/scala/scala-2.12.10.ebuild
signature.asc
Description: OpenPGP digital signature
