Updating VM links for Pharo 1.1

2010/7/7 Mariano Martinez Peck <[hidden email]>:

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

Regards,
--
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

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 <
> [hidden email]> wrote:
>
>> 2010/7/7 Mariano Martinez Peck <[hidden email]>:
>>> 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
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

- I updated the Mac VM link to point to version 4.2.5beta1U. This version certainly also makes sense for Pharo 1.0.

- I didn't change the other links since the Windows one already points to the proposed version (4.0.2)

and the Unix link does not point to a specific version.

So no need to have a separate set of links if they are all the same.

Does that make sense?

Cheers,
Adrian

On Jul 8, 2010, at 02:59 , Schwab,Wilhelm K wrote:

> One concern: having separate download links in no way tells us what vm someone uses with a particular version, and we can't assume that it does.
>
>
>
> ________________________________________
> From: [hidden email] [[hidden email]] On Behalf Of Mariano Martinez Peck [[hidden email]]
> Sent: Wednesday, July 07, 2010 6:11 PM
> To: [hidden email]
> Subject: Re: [Pharo-project] Updating VM links for Pharo 1.1
>
> On Wed, Jul 7, 2010 at 2:19 PM, Adrian Lienhard <[hidden email]<mailto:[hidden email]>> wrote:
> I'm a bit confused. Do we want to have a separate set of VMs or not?
>
> Yes, I vote to put them separated.
>
> Furthermore, the link to the Unix VM just goes to http://squeakvm.org/unix/, but not to a particular version.
>
>
> As far as I know, there is not way to link to a particular version. You can, but to a particular version/platform (for example, GNU/Linux, FreeBSD, etc...)
>
> Cheers,
> Adrian
>
>
> On Jul 7, 2010, at 14:09 , Mariano Martinez Peck wrote:
>
>> On Wed, Jul 7, 2010 at 11:33 AM, Serge Stinckwich <
>> [hidden email]<mailto:[hidden email]>> wrote:
>>
>>> 2010/7/7 Mariano Martinez Peck <[hidden email]<mailto:[hidden email]>>:
>>>> 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
>>> [hidden email]<mailto:[hidden email]>
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]<mailto:[hidden email]>
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]<mailto:[hidden email]>
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Hello

What plans about Cog?

It will be good if you provide builded Cog VM with prepared Pharo release image.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project