[Pkg-squeak-devel] newbie in the squeak&debian world

[Pierre Boutillier]

Le 25 janv. 12 à 19:54, Bert Freudenberg a écrit :

> On 25.01.2012, at 10:47, José Luis Redrejo Rodríguez wrote:
>
>> 2012/1/25 Bert Freudenberg <bert at freudenbergs.de>:
>> I think he should use http://packages.debian.org/squeeze/etoys for  
>> the image
I do and it is OK in the first time even if I think that trying to put  
it in main will be the next challenge after vm issue.
It means in my opinion bootstrap from source the most convienent  
squeak image to bootstrap and then recreate images by reapplying  
changesets + adding default projects +.... I may be completly wrong  
and in any case, this comes after having an up to date vm in testing !
>>
>>>
>>> An additional complication is that there are now multiple VMs -  
>>> the original interpreter ("Squeak VM") and a jit compiler (called  
>>> "Cog VM"). The jit is x86 only for now so there is a special  
>>> interpreter (a.k.a. "Stack VM") that is compatible with the jit  
>>> for non x86 platforms. Both the jit and the interpreter need to be  
>>> installed at the same time to be able to run older images. The  
>>> best way to package it IMHO would be to have two binaries in the  
>>> package and the squeak-vm script chooses the appropriate one based  
>>> on the image version. But because the jit is relatively new, not  
>>> even upstream has this scheme in place.
>>>
>>
>> Bert, I'm not following the Cog development (I'm an amd64 user in all
>> my machines), but as far as I understand from your message: to  
>> package
>> the vm correctly, two different sources should be compiled , one
>> compiled in x86 , and the other in the rest of the architectures.  
>> That
>> doesn't make two much sense for one package, so it seems that a cog- 
>> vm
>> package would need to be introduced for the x86 support and leaving
>> the rest of architectures with the current squeak-vm virtual machine
>>
>> am I right?
>
> Almost - we still need the current squeak-vm (to be able to run e.g.  
> etoys) plus cog-vm (on x86) and stack-vm (all archs). Etoys does not  
> work on cog-vm/stack-vm so we still need squeak-vm.


Why not
- renaiming squeak-vm squeak-original-vm(randomly chosen name)
- creating a virtual all arch package squeak-vm on which images will  
depend
- make an x86 package coq-vm that implements in preference squeak-vm  
and an any arch package stack-vm that also implements squeak-vm. (I  
don't undertand if squeak-original-vm should implements squeak-vm by  
it could to)
- make etoys explicitly depends on squeak-original-vm for now

By the way, it is cosmetic but I don't see why is squeak-vm depends on  
a x-terminal-emulator.

Pierre