Arch Linux

It is separate project
http://akka.io/
http://typesafe.com/stack/downloads/akka

If you find something missing (not compiled into package) from scala-source-2.10.0.tgz please let me know.

This is no longer a separate project, it's in process of being merged and that's why it's included in source. Check:

http://docs.scala-lang.org/overviews/core/actors-migration-guide.html

It says:

"""In Scala 2.10.0 actors reside inside the Scala distribution as a separate jar ( scala-actors.jar ), and the their interface is deprecated. The distribution also includes Akka actors in the akka-actor.jar. The AMK resides both in the Scala actors and in the akka-actor.jar. Future major releases of Scala will not contain Scala actors and the AMK."""

It means, that our package includes only deprecated version of library instead of one that is shipped upstream as part of official distribution - and we will never ship migration toolkit, because when akka will be merged there will be no AMK. If we assume that it should still be separate project, then I blieve scala package should depend on akka package or provide it anyway.

It could be probably solved easily by providing official built distribution instead of building our own? If we consider scala to be a java package, our wiki at https://wiki.archlinux.org/index.php/Java_Package_Guidelines says we do not have to compile java packages as it does not give us much. Is there any reason why you decided to build it from source? I haven't checked it, so I might not know.

To be more exact, those are missing libraries that are bundled with Scala binary distribution:

Akka Actors 2.1.0: akka-actors.jar ( http://akka.io/ )
Scala Actors Migration 1.0.0: scala-actors-migration.jar ( https://github.com/scala/actors-migration )
Typesafe config 1.0.0: typesafe-config.jar ( https://github.com/typesafehub/config )

And we have one extra file, which gets removed from official distribution: scalacheck.jar

All this is defined in file https://github.com/scala/scala-dist/blob/master/project/scaladistrofinder.scala function "cleanScalaDistro" - it does 3 things:

- dos2unix on *.bat files (not applicable for us)
- remove scalacheck.jar
- download those 3 extra .jar files from Maven repository

Now goes the question - what do we consider to be "upstream" in this case? Officially published sources, or officially published binaries?

And one more thing - reasons why they remove scalacheck.jar:

- https://groups.google.com/forum/#!topic/scala-internals/gqDXK6tofGc
- https://issues.scala-lang.org/browse/SI-6121 (marked as critical bug)

Still, I don't know why they build and install it as part of process, probably to have compatible/same version of ScalaCheck for checking compiler during its development. This makes me think that we should conform to binary version, not source version. Just my though though, what do you think?

I adjusted ticket description to mirror new findings about why our scala differs from distributed scala.

As a reference I've created 3 packages that install missing jar files:

https://aur.archlinux.org/packages/scala-actors-migration/
https://aur.archlinux.org/packages/scala-akka-actors/
https://aur.archlinux.org/packages/scala-typesafe-config/

this can serve as temporary solution, but it does not solve issue with scalacheck.jar that should be removed.

thanks, probably I'll move them to community.

@Sergej, any decision? I think it would be fine to use the prebuilt jar files, as we don't get too much optimization by building them from sources.

scala 2.10 cannot be build using java7. Waiting for 2.11 wich should be compatible with java7. Maybe it is ok to use binaries.

I attached a PKGBUILD for scala 2.10.3, which uses the prebuilt jar files released by upstream.

@Sergej, would you accept this PKGBUILD?

Now I released the new scala-2.10.3-1 package, it's available in the [community-testing] repository. Please let me know if I did something wrong.