2010/3/28 Mariano Martinez Peck <[email protected]> > > >>> If someone is interested, these are all the packages I needed to install >>> in order not to have problems in my Ubuntu 9.10: >>> >>> sudo apt-get install linux-libc-dev libecasound2.2-dev libasound2-dev >>> libc6-dev gnulib libc6-dev libpulse-dev libxrender-dev uuid-dev >>> >> >> Should be on Pharo website, given the popularity of Ubuntu. >> > > > 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.zip > > Yes.
> From 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 > I don't know, my system is 32 bits, don't have the courage to install a 64 bits one :) > - 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. > - 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". > Yes, I'm one of those people :) > - 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. > I haven't been able to build Exupery ... > - 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 ? 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 >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
