I'm a bit confused. Do we want to have a separate set of VMs or not? 
Furthermore, the link to the Unix VM just goes to http://squeakvm.org/unix/, 
but not to a particular version. 

Cheers,
Adrian


On Jul 7, 2010, at 14:09 , Mariano Martinez Peck wrote:

> On Wed, Jul 7, 2010 at 11:33 AM, Serge Stinckwich <
> [email protected]> wrote:
> 
>> 2010/7/7 Mariano Martinez Peck <[email protected]>:
>>> Hi. Henry made me remember that we need to update the VMs links for Pharo
>>> 1.1. We are in RC4 and very very near of the stable release. Thus, I
>> suggest
>>> to fix this problem.
>>> 
>>> You can see in http://code.google.com/p/pharo/issues/detail?id=2646
>>> 
>>> Mac:
>>> 4.2.5
>>> Windows:
>>> 4.0.2
>>> Linux:
>>> 4.0.3.2202
>>> 
>>> What I am not sure if we should put these links in a particular section
>> of
>>> Pharo 1.1 or just update the current VMs links. The problem of doing the
>>> last one is that these VMs will be downloaded for both images: 1.0 and
>> 1.1.
>>> Are there problems with it ?   The only thing I can image is if the vm
>> has
>>> FreeType compiled.
>> 
>> Hi Mariano,
>> 
>> maybe it's better to avoid problems by providing two distincts VMs.
>> And if some people reports problem from 1.0, maybe you will not know
>> wich VMs they used.
>> 
> 
> +1. I completly agree.
> 
> Adrian, could you do this please?
> 
> Thanks
> 
> Mariano
> 
> 
>> Regards,
>> --
>> Serge Stinckwich
>> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
>> Every DSL ends up being Smalltalk
>> http://doesnotunderstand.org/
>> 
>> _______________________________________________
>> 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

Reply via email to