small refactor on files.pharo.org

On 05 Jan 2016, at 19:14, Andrei Chis <[hidden email]> wrote:

What's the recommended way of loading the VM through zeroconf  scripts?

Just http://get.pharo.org/vm loads the non-spur vm and http://get.pharo.org/vm50 loads the spur one. Will http://get.pharo.org/vm be updated to the spur one in the future?

Cheers,

Andrei

On Tue, Jan 5, 2016 at 11:47 AM, Esteban Lorenzano <[hidden email]> wrote:

I move old VMs from files.pharo.org/vm to files.pharo.org/vm/old

because it was confusing and some students were lost (Stef too :P). 

cheers,

Esteban

On 05 Jan 2016, at 20:06, Dimitris Chloupis <[hidden email]> wrote:

but this still works as expected yes ?

wget -O- get.pharo.org/alpha+vmLatest | bash

On Tue, Jan 5, 2016 at 8:23 PM Esteban Lorenzano <[hidden email]> wrote:

On 05 Jan 2016, at 19:14, Andrei Chis <[hidden email]> wrote:

What's the recommended way of loading the VM through zeroconf  scripts?

Just http://get.pharo.org/vm loads the non-spur vm and http://get.pharo.org/vm50 loads the spur one. Will http://get.pharo.org/vm be updated to the spur one in the future?

Hi,

no it will not be updated. 

In fact if you see is not listed anymore (since almost one year now). It is just there for backward compatibility.

you need to use the VM corresponding with your image version (in case of Pharo 50, vm50).

Esteban

ps: this was described when I made the change like one year ago… but now I do not find the mail :P

Cheers,

Andrei

On Tue, Jan 5, 2016 at 11:47 AM, Esteban Lorenzano <[hidden email]> wrote:

I move old VMs from files.pharo.org/vm to files.pharo.org/vm/old

because it was confusing and some students were lost (Stef too :P). 

cheers,

Esteban