Summary: | dev-lang/scala-2.11*: some scala-* libraries are missing the ".jar" ending | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Walch <walch.martin> |
Component: | [OLD] Java | Assignee: | Java team <java> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | monsieurp |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Walch
2014-12-16 11:29:51 UTC
Err, after submitting, now I see that it is a bit more complicated. Probably it has something to do with the underscore vs hyphen to separate version numbers. (Anyway, I did not investigate this in depth as I do not know much about the Gentoo Java stuff) Thanks for reporting. This is what we get during the build: argus lib # pwd /var/tmp/portage/dev-lang/scala-2.11.4-r002-jdk-1.7-source-of-binary/work/scala-2.11.4/build/pack/lib argus lib # ls -al total 24996 drwxr-xr-x 2 portage portage 15 Nov 27 12:12 . drwxr-xr-x 7 portage portage 9 Nov 27 12:18 .. -rw-r--r-- 1 portage portage 213854 Nov 27 12:11 jline.jar -rw-r--r-- 1 portage portage 465732 Nov 27 12:12 scala-actors.jar -rw-r--r-- 1 portage portage 13481629 Nov 27 12:11 scala-compiler.jar -rw-r--r-- 1 portage portage 25365 Nov 27 12:12 scala-continuations-library_2.11-1.0.2.jar -rw-r--r-- 1 portage portage 206573 Nov 27 12:12 scala-continuations-plugin_2.11.2-1.0.2.jar -rw-r--r-- 1 portage portage 5473676 Nov 27 12:11 scala-library.jar -rw-r--r-- 1 portage portage 416065 Nov 27 12:12 scala-parser-combinators_2.11-1.0.2.jar -rw-r--r-- 1 portage portage 175445 Nov 27 12:12 scala-partest-extras.jar -rw-r--r-- 1 portage portage 4839 Nov 27 12:12 scala-partest-javaagent.jar -rw-r--r-- 1 portage portage 756095 Nov 27 12:12 scalap.jar -rw-r--r-- 1 portage portage 4342217 Nov 27 12:11 scala-reflect.jar -rw-r--r-- 1 portage portage 726500 Nov 27 12:12 scala-swing_2.11-1.0.1.jar -rw-r--r-- 1 portage portage 648678 Nov 27 12:12 scala-xml_2.11-1.0.2.jar argus lib # I will rename them to strip the version numbers from the end (which do not seem to match upstream's binary anyway), using something like: argus lib # for i in *.jar; do echo "$(echo "${i}" | sed -e "s@_\?[0-9.-]*\.jar@.jar@")"; done jline.jar scala-actors.jar scala-compiler.jar scala-continuations-library.jar scala-continuations-plugin.jar scala-library.jar scala-parser-combinators.jar scala-partest-extras.jar scala-partest-javaagent.jar scalap.jar scala-reflect.jar scala-swing.jar scala-xml.jar argus lib # The classpath of all the jars can be obtained with: java-config -p scala It also seems time to drop some old versions and to work on bumping it to 2.11.5. (In reply to Mark Wright from comment #2) > It also seems time to drop some old versions and to work on bumping it to > 2.11.5. When doing so, can you keep the newest versions of the 2.9 and the 2.10 release series around? Actually needing Scala 2.9.x has become rare, but there are quite some projects (not in the portage tree) that are still incompatible with Scala 2.11 and therefore still need Scala 2.10. Also: would it be feasible to slot the ebuilds for parallel install (like SLOT="2.x")? Fixed: Thanks to Martin Walch for reporting, fix Bug 532694 - dev-lang/scala-2.11*: some scala-* libraries are missing the ".jar" ending. Drop old versions. (In reply to Martin Walch from comment #3) > (In reply to Mark Wright from comment #2) > > It also seems time to drop some old versions and to work on bumping it to > > 2.11.5. > > When doing so, can you keep the newest versions of the 2.9 and the 2.10 > release series around? Sure, kept just for you :-) > Actually needing Scala 2.9.x has become rare, but > there are quite some projects (not in the portage tree) that are still > incompatible with Scala 2.11 and therefore still need Scala 2.10. Also: > would it be feasible to slot the ebuilds for parallel install (like > SLOT="2.x")? It appears that to install in multiple slots it would have to somehow avoid collisions on: /usr/share/man/man1 /usr/share/scala/src I'm unsure if the java eclasses would avoid those ones. I think they would avoid the collisions on: /usr/share/scala/lib /usr/share/scala/bin The ebuild could append the version numbers to the /usr/bin symlinks. Fixed. |