Re: old version of scala
On 07.02.2019 15:29, Thorsten Glaser wrote:
On Thu, 7 Feb 2019, Thomas Finneid wrote:
downloads and installs the required scala and sbt version inside the project
This is absolutely not going to happen in Debian.
I might have been a litte unclear by my wording, when I said scala/sbt
proejct, I meant one of two things, depending on context:
1- the scala development teams project files
2- the end users scala project files
but all sbt projects installs into the current project the specified
scala verison and sbt version. But that is just inside the current
project and its build environment. It does not affect the system as a
whole or any other sbt projects, its sort of like the maven target dir.
But it only requires an sbt installation and a user .sbt directory to
hold it all.
You can always do it like e.g. the GNAT people do:
build-depend on the previous version.
That is, assuming the current scala (2.11?) can build a new enough
sbt and scala to build the latest version, or somesuch.
If there’s no such path, you’d need more intermediate versions and
upload them, one after another. Into experimental would most likely
be the best, with the understanding that these are intended for
bootstrapping, not for use by users, although they could, in theory,
One thought, both the scala team and the sbt team produces .deb
packages, can they be uploaded as final distribution packages, or even
used as the the toolchain package on the CI system?
If not, then using the current sbt-ivy and scala 2.11 packages with jdk8
will probably be a long roundtrip of part- upgrades, as there is a
slightly complex compatability matrix for scala, sbt and jdk together to
reach 2.12.8, with a build that has its build intregrity in order. I
will have to check the details on that,
So to build on CI system, is it allowed to preconfigure it manually with the
newest sbt version, i.e. version 1.x, from a tarball download?
Ok? Do I understand it correctly that everything has to be built from
scratch and the build system can only to be configured using debian
How can one introduce new things into the system for which there is no
preexisting package or toolchain?