Am 14.02.19 um 22:59 schrieb Thomas Finneid:
[...]
> Either this is what I had in mind originally or some detail is missing.
>
> Said another way, the rules script is in two parts. The first part is
> used in experimental, to download external sbt tools to bootstrap the
> build of the pre-version
On 14.02.2019 18:19, Markus Koschany wrote:
Experimental is merely a playground for developers who think their
packages are not ready for unstable yet. What you usually do is to
bootstrap the package and build all those parts that are essential to
get a functional compiler/build tool. Then
Am 14.02.19 um 17:45 schrieb Thomas Finneid:
> On 14.02.2019 11:55, Markus Koschany wrote:>
>
>> What you can do of course is to patch sbt or scala. We use so-called
>> quilt patches. For instance take a look at sbt. In debian/patches you
>> can see several Debian specific patches that change
On 14.02.2019 11:55, Markus Koschany wrote:>
> What you can do of course is to patch sbt or scala. We use so-called
> quilt patches. For instance take a look at sbt. In debian/patches you
> can see several Debian specific patches that change the default Maven
> repository for example.
Thats
Am 14.02.19 um 00:22 schrieb Thomas Finneid:
>
>
> On 12.02.2019 22:40, Markus Koschany wrote:
>> There are different rules for contrib and non-free. [1] You could
>> package scala and sbt for contrib, because both pieces of software
>> comply with the DFSG. If you use a prebuilt package for
Hi Thomas,
[I add debian-java back to CC in case someone else can reply with
something helpful]
Am 12.02.19 um 22:17 schrieb Thomas Finneid:
>
>
> On 08.02.2019 22:12, Markus Koschany wrote:
>> First of all thank you for your interest in helping us to improve Scala
>> in Debian. Unfortunately
On Thu, 7 Feb 2019, Thomas Finneid wrote:
> 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
One thing to remember is that we do NOT upload .deb packages.
We upload .dsc packages (Debian
Hi Thomas,
Am 08.02.19 um 03:54 schrieb Thomas Finneid:
[...]
> I have been trying to read some of the documentation on package
> mainteneance, especially "Debian New Maintainers' Guide" and the newer
> "Guide for Debian Maintainers".
> I havent been able to find yet, any documentation that
Sorry for all the confusing questions, but getting to know a new build
process, especially such an advanced one as Debians, is quite
confusing to begin with.
On 08.02.2019 02:29, Thorsten Glaser wrote:
On Thu, 7 Feb 2019, Thomas Finneid wrote:
One thought, both the scala team and the
On Thu, 7 Feb 2019, Thomas Finneid wrote:
> 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?
No, of course absolutely not.
> > > So to build on CI
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
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.
> With these facts at hand, the question is how to deal with this in the debian
> build system?
You can always do it like
Hi
Having dug a little deeper into building scala 2.12.8, I have found two
issues that needs some explaining.
Scala and sbt environemnts are a bit different from the ordinary java or
C environments.
I know there already exists scala and sbt packages in debian, but as far
as I understand
On 05.02.2019 16:40, Thorsten Glaser wrote:
Then, yes, an upgrade to 2.12 should be done. Using the new --release
option in javac 11, it can be built looking as if it were using JDK 8,
but JRE 8 is not really available any more either (I believe the idea
was to ship buster without
On Tue, 5 Feb 2019, Thomas Finneid wrote:
> So a Linux system that uses a jdk higher than java 6 for running scala
> code with scala 2.11, can experience unexpected faults or errors while
> running a scala program Likewise with scala 2.12, it is built and
> tested using java 8.
Then, yes, an
Apologies for the iPhone typo: last paragraph about sbt, I never meant to type
“ant 1.x” but rather “sbt 1.x”
Thomas
Sendt fra min iPhone
> 5. feb. 2019 kl. 15:08 skrev Thomas Finneid :
>
> Hi
>
> What I mean is that the scala projects own build process built and tested
> scala 2.11
Hi
What I mean is that the scala projects own build process built and tested
scala 2.11 using java 1.6.
Scala 2.12 is built and tested with java 8.
So a Linux system that uses a jdk higher than java 6 for running scala code
with scala 2.11, can experience unexpected faults or errors while
On Mon, 4 Feb 2019, Thomas Finneid wrote:
> NB1: Scala 2.11 is built for java 6, and has only rudimentary support for java
> NB2: Scala 2.12 is built against java 8, so it does not support java 9/10 or
What do you mean “built for/against”?
In Debian, the Scala source code is built against the
18 matches
Mail list logo
