�

- 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.

I agree we need to explain better the distinction between the VM and the image. I'm not sure about renaming squeak-vm -> pharo-vm. It's not a fork. I tend to think it will bring higher confusion.

I don't agree. Image you are a new comer. For you, Pharo is Pharo. You probaly have no idea what Squeak is. So...you go to Pharo website, and download the image, and the VM. Imagine when you go to download the VM and it says "SqueakVM". I would say "WTF?????"�� "WTF is squeak?"
I am not saying forking the VM. Just to rename it. Actually, the windows VM has that name: "http://gforge.inria.fr/frs/download.php/26654/PharoVM-Win32-3.11.8.zip"
And the same with exupery: "http://gforge.inria.fr/frs/download.php/24736/pharo-vm-0.15.2f-linux.zip"

�

�

�

- 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.

Agree.

Maybe you can open a git repository on INRIA servers so we can keep track of patches + README included in the VM for Pharo. I've used Javier and Levente patches and these are not included in squeak-vm svn. I sent a mail last week on vm-dev but no answers.
This way builders can do:
git clone git://......squeak-vm
cd ..squeak-vm../build
... configure && make && make install.
For packagers it would be cool.
Developpers can have their own branches and submit patches more easily, add more visibility.
With git-svn we can synchronize from official Squeak-VM svn (until they switched to git or another DVCS :)

What do you think ?

I like the idea....but what about the sync with the public/official SVN repo ? how we will be able to merge ? or the GIT repo will be only for patches ?

Cheers

Mariano

�

Laurent Laffont
�

Cheers

Mariano

�

Ok.....but not only plugins. For exaple, if I don't want UTF-8 ?

errr... maybe it's time to ask to the vm-dev list :)

�

ufff.....what an idiot...thanks!� did you already discovered I am a newbie here ? :)

Me too, but a little less every day :)

Laurent Laffont

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project