Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enter current Scala version (2.12.1) into next Debian stable (Stretch) #10172

Closed
scabug opened this issue Feb 4, 2017 · 5 comments
Closed

Enter current Scala version (2.12.1) into next Debian stable (Stretch) #10172

scabug opened this issue Feb 4, 2017 · 5 comments

Comments

@scabug
Copy link

scabug commented Feb 4, 2017

The next Debian version, Stretch, is becoming a stable release soon, with hard freeze happening in the next days. Scala is still at 2.11.8: https://packages.debian.org/sid/scala

As I understand the problem with submitting 2.12.1 is that it requires sbt to build. I think a zero-dependencies variant of building the Scala package is to simply include Paul Philips' "sbt" shell script which takes care of getting the right version of sbt when trying to build.

@scabug
Copy link
Author

scabug commented Feb 4, 2017

Imported From: https://issues.scala-lang.org/browse/SI-10172?orig=1
Reporter: @Sciss
Affected Versions: 2.12.1

@scabug
Copy link
Author

scabug commented Feb 4, 2017

@retronym said:
Our understanding is that SBT is not acceptable as a build tool in general, and we would need to somehow export our build to Ant or Make to qualify for Debian. The most recent discussion about the constraints is in scala/scala#5311 (comment)

We don't have the resources to take on this task. We do offer a .deb package (linked from https://www.scala-lang.org/download/2.12.1.html), but I realise that this isn't quite the same as having a package pre-installed with Debian.

@scabug
Copy link
Author

scabug commented Feb 4, 2017

@martijnhoekstra said:
sbt-extras is not a solution for the problem: the build must be offline.

sbt-extras in itself as a package could be nice though.

@scabug
Copy link
Author

scabug commented Feb 25, 2017

@SethTisue said (edited on Feb 25, 2017 5:25:46 PM UTC):
Sometimes people interested in building Scala from source for packaging purposes, or interested in compiler development in general, assume that it should be possible to recreate the current version of Scala by following a chain of an older versions, building every version N + 1 using version N, back to some zero.

It's certainly a reasonable thought to have. In theory, this would be possible with Scala, but only in theory, not in practice. It certainly isn't as easy as building 2.12 with 2.11, building 2.11 with 2.10, and so forth. That definitely doesn't work. The Scala 2.12 compiler is written in Scala 2.12, not Scala 2.11, and so on for previous versions. We've re-STARRed countless times, so the chain of previous versions is now very very very long... (in the hundreds, I imagine?).

Even getting back to the last version of Scala that was built with ant instead of sbt is not a practical or recommended approach, and will only get less practical and less recommended as the ant->sbt changeover recedes further into the past.

A discussion on this from fall 2016 begins here: scala/scala#5381 (comment)

Anyway, a word to anyone interested in packaging: starting with an older Scala won't help you. You must figure out a way to build the current Scala using STARR. (Once it's built, you can go on and rebuild it with itself, if you want. The result will be the same; that's the "stability check", which we perform in the Scala CI, as part of the "integrate-bootstrap" script.)

@SethTisue
Copy link
Member

duplicates #9299

@SethTisue SethTisue closed this as not planned Won't fix, can't repro, duplicate, stale Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants