#43124: New port: scala2.11 -------------------------+-------------------------------- Reporter: msa@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: scala2.11 | -------------------------+-------------------------------- Comment (by msa@…): Hi Blair, Which scala jar files do your scripts use? I see two other alternatives to maintaining individual file symlinks in the Portfile: 1. Create a symlink from share/java/scala-2.11 to share/scala-2.11/lib. Client scripts use a strategy described in http://stackoverflow.com/questions/4729863/using-bash-how-do-you-make-a -classpath-out-of-all-files-in-a-directory to create a classpath from all jar files in share/java/scala-2.11. 2. Like (1), but don't create the symlink. Clients pull jar files from share/scala-2.x/lib. This strategy has the advantage that compatible scripts can be easily adapted to use either scala 2.10 or 2.11 (or 2.9, presumably, though I haven't checked its layout). Cheers. -- Ticket URL: <https://trac.macports.org/ticket/43124#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X