I was thinking to add that to the readme.txt. Laurent, can you please
download VM:
http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zipFrom
my point of view, we need to distribute a Linux VM that:
- Has a easy way to install. I think your VM is cool in these point.
I found Exupery a bit more tricky.
- Has FreeType installed
-
Has an EXCELLENT README.TXT that explains how to compile from source,
how to install it, how to use it, and a FAQ for tipical questions. For
example, in Ubuntu, these libraries has to be installed in order to
compile. What happend with 64 bits? All that has to be explained in that
file
- In the README.TXT we also have to put links for help: squeakvm site,
posts like Laurent or Adrain
- Gunification
- It needs to have a
name of PharoXXX. Not squeak. This is VERY confusing for newcomers.
-
It has to include sources. I know a lot of people that says "I won't
put anything in production that I cannot compile by myself first".
- It has to be a Standard VM, not Exupery. Exupery without the exupery
package, has no sense at all. It is in Pharo download just because of
history reasons. Bryce was very helpful and was the first in put
closures in the VM. So, we used that. Now, it has no sense anymore.
- Pass all PharoRC3 tests in green
- The process has to be
repeatable. Someone has to be able to came in 1 year, donwload the same
VM and repeat the steps without major problems.
- The readme.txt has
to include the SVN revision where the C code was taken.
- It would also be good to said which ConfigurationOfVmMaker version was
used.
Cheers
Mariano
�