<div style=""><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">
</span><div><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">
</span></div><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">
</span><div><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">
</span></div>
</div><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">
</span><div style=""><div><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">Hi David,</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">Answering below</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">El viernes, 12 de junio de 2026 a las 13:18, David Goodenough <david.goodenough@broadwellmanor.co.uk> escribió:</span><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">
</span><blockquote type="cite"><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">I think that 3.8 also uses the scala_3 library. 3.8 was a kind of RC for 3.9 so they wanted to make the breaking changes first before jumping to what it an LTS release.</span></p>
</blockquote><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><br></p><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">Good to know, and good to remember when reach the scala 3 stage, thanks!</span></p><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><br></p><blockquote type="cite"><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">SBT and Scala-CLI will always use the cached versions of the libraries it finds from Maven (or which ever repository you specify), and if you update the dependencies on your build file or script it will always go and fetch the new version from the repository. The cache lives in the user's directory, and I don't think there is a system wide cache that debian packages could populate.</span></p>
<br><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">This also applies to the compiler and all its support libraries.</span></p>
<br><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">So yes, the virtuslabs .debs do not try to package libraries, just the sbt and scalacli. Because that is the way the scala build system works.</span></p>
<br><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;"><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">Packaging the compiler and the libraries is only of use if you want to run them manually, and no-one does that.</span></p></blockquote></div><div><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">I believe we are agreeing at the end, but just to clarify, because I believe both ways servers different and compatible purposes:</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">- Your approach: Having sbt + scala-cli so a developer</span><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;"> can use Scala on Debian, with Coursier fetching their dependencies on demand. That's a separate effort that can be pursued</span><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;"> independently — and would be valuable in its own right.</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">- My suggestion (and the RFP): package the compiler and libraries from source so they can be </span><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">build-dependencies for other Debian packages</span><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;"> — Scala applications like Spark, Metals,</span><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;"> Joern, and the existing Scala rdeps. They need to build from source, offline, in the archive. None of those can enter Debian until the toolchain is there.</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">So as a recap, tools and libraries: they serve different users (yours the developer, "mine" the Debian packages) and the two efforts don't block each other. That second</span><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;"> goal is the one I'm after.</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">Let me know if I got this correct, our you found any flaw.</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">Best,</span><br><br><span style="font-family: Arial, sans-serif; font-size: 14px; line-height: normal; font-weight: 400;">Juan</span></div></div>