[Pharo-dev] Pharo VM latest on the Debian 7
avalloud at smalltalk.comcastbiz.net
Sun Aug 11 09:39:46 EDT 2013
Ok, thank you. At the risk of being too inquisitive, what do you mean
when you say "add a slave into our build server"? Is the implication
that a release will include N binaries compiled on N Linux versions?
On 8/8/13 8:02 , Esteban Lorenzano wrote:
> well... no.
> something happened with the build, because it should be executable in a 1.5 years old linux.
> in the middle term, we are going to adopt an approach similar to VW (one VM for one image version), and we will support some years of backward compatibility.
> But not infinite, of course, because work is too much :)
> Now... the "latest" VM is unstable. Is not a release and of course it will be problems.
> When we release it, it will be version to run in several versions... it should be as simple as add a slave into our build server.
> On Aug 8, 2013, at 4:54 PM, Igor Stasenko <siguctua at gmail.com> wrote:
>> On 8 August 2013 15:40, Andres Valloud
>> <avalloud at smalltalk.comcastbiz.net> wrote:
>>> Are you saying the Pharo VM requires glibc version 2.15 of March 2012, and
>>> that consequently the Pharo VM as compiled won't run on any Linux distro
>>> older than 17 months?
>> You are not forced to use latest VM, you can always download and use
>> 5-year old VM, which will (hopefully)
>> work for you.
>> Now if platform (linux) moves, we must follow. And that is not a question to me.
>> Best regards,
>> Igor Stasenko.
More information about the Pharo-dev