In that case, the answer is yes. The Scala package will be published in one version with a variaty of backend package choices. User can easily attach and detach different MXNet versions. However, the Scala package cannot run without a backend.
Another key advantage of this design will be a broader support on different implementations such as Java Cpp. User will be able to implement their customized MXNet frontend to use the native library. Thanks, Qing ________________________________ From: Sheng Zha <szha....@gmail.com> Sent: Tuesday, July 2, 2019 22:14 To: dev@mxnet.incubator.apache.org Subject: Re: [DISCUSS] Make MXNet deploy it's own distribution Does it mean that the scala binding of mxnet will be an independent package that doesn’t directly depend on the native package, and user projects need to declare dependency on both the scala binding and one of the native packages? -sz > On Jul 2, 2019, at 5:50 PM, Frank Liu <frankfliu2...@gmail.com> wrote: > > Currently, MXNet were built along with different language bindings such as > Scala. > > The libmxnet.so files are bundled within scala jar package. > > It would be nice to distribute libmxnet.so library independently in maven, > and scala package can choose which native library to use. > > Here is the design document on cwiki: > https://cwiki.apache.org/confluence/display/MXNET/Make+MXNet+deploy+it%27s+own+distribution > > Thanks, > > Frank
