Re: [Sablevm-developer] Short release status - almost there...

[Grzegorz B. P. <ga...@de...>]

W li=B6cie z nie, 15-02-2004, godz. 09:41, Etienne Gagnon pisze:=20
> Chris Pickett wrote:
> >> 2. Updated http://devel.sablevm.org/docs/INSTALL.txt document, which
> >> serves as both: release notes and installation instruction, and put =
it
> >> into sablevm/staging as INSTALL-DEVEL text file (made it included in
> >> the "dist" tarball - should be removed on migration to trunk!).
> >=20
> >=20
> > Seems like common practice would be to put a single INSTALL file in t=
he=20
> > top level of sablevm.
>=20
> I agree with the INSTALL file.

Well, I could simply rip-off the upper part of the file, which says
things about "build" and "build-many" scripts, downloading 3 tarballs,
etc. In general all that seems rather outdated. The question is
whether we want to keep any of this stuff? There's no build script in
staging's sablevm.

If you don't mind - then I'll go and put current build instructions
there instead. And split news into NEWS. This should probably be done
before tagging 1.1.0 in bugfree.

> Another thing:  I do really think that "./configure ; make ; make insta=
ll"
> should work out-of-the-box for sablevm-x.y.z.tar.gz and for
> sablevm-classpath-x.y.z.tar.gz.  Currently, it is broken for
> sablevm-classpath (as you need to pass specific configure options to ge=
t
> a sablevm usable build).  Assume that the typical user WILL NOT read th=
e
> README file nor the INSTALL files and will simply go ahead and type the
> standard commands above.  [Alternatively, you could make sure that
> "./configure" fails for sablevm-classpath, and issues a message invitin=
g
> the user to read the README and INSTALL files...]

I agree. Any takers? That should be just some playing w/ configure's
defaults, so that --prefix was enough to set --libdir and --datadir
properly to sablevm's needs. (though I don't see it as 1.1.0
showstopper).

> The worst situation is if a user does the standard commands, gets no bu=
ild
> error message, yet gets "could not start vm" when trying to run HelloWo=
rld.
>=20
> What do you think?

This will be our first (and most used) FAQ entry. *g*
(and there's more than one answer to that too)

Cheers,

					Grzegorz B. Prokopski

--=20
Grzegorz B. Prokopski <ga...@de...>
Debian GNU/Linux      http://www.debian.org
SableVM - LGPLed JVM  http://www.sablevm.org
Why SableVM ?!?       http://devel.sablevm.org/wiki/WhySableVM