RE: using nightly build

Yes, the problem is the ch.epfl stuff is in the same directory - which
is what I was looking at. The very top file listed is a
"...2.8.0.latest.zip" containing scala jars, hence my confusion.
Tim

-----Original Message-----
From: Antonio Cunei [mailto:scala_ml@cunei.com]
Sent: 07 May 2009 22:32
To: scala-user@listes.epfl.ch
Subject: Re: [scala-user] using nightly build

On Thu, May 7, 2009 10:50 pm, Paul Phillips wrote:
> On Thu, May 07, 2009 at 09:14:21PM +0100, Tim Pigden wrote:
>> jar files with names that bear little relation to the named jar files
>> in the scala distribution.
>
> Wow, this page is unnecessarily intimidating:
>
> http://www.scala-lang.org/node/212
>
> It would be great if someone could put the most likely to be relevant
> links up top - those being scala-2.8.0.latest.* which are presently
> about ten screenfuls down.
>

The page is just the prettified form of a directory listing, in which
the
results of the nightly builds are unceremoniously dumped. The nightly
builds list is quite appropriately intimidating, I find, as looking at
them should communicate fear and danger.

Jokes aside, the content of the various jars and zips in the nightly
directory is actually the same as the content of the regular
distribution.
For example, this tgz:

http://www.scala-lang.org/archives/downloads/distrib/files/nightly/scala
-2.8.0.latest.tgz

contains the following:

$ ls -d */*
bin/fsc bin/scalap.bat lib/scalap.jar
bin/fsc.bat doc/LICENSE man/man1
bin/scala doc/README src/scala-compiler-src.jar
bin/scala.bat doc/scala-devel-docs src/scala-dbc-src.jar
bin/scalac lib/scala-compiler.jar src/scala-library-src.jar
bin/scalac.bat lib/scala-dbc.jar src/scala-partest-src.jar
bin/scaladoc lib/scala-library.jar src/scala-swing-src.jar
bin/scaladoc.bat lib/scala-partest.jar src/scalap-src.jar
bin/scalap lib/scala-swing.jar

which is the same as the tgz of the main distribution, as documented at
the page http://www.scala-lang.org/node/36. As Paul observed, just
adding
the 'bin' directory to the path, regardless of where the tgz was
expanded,
should be sufficient.
Toni