[Vm-dev] Problems building rev 2181 on Linux

Andreas Raab andreas.raab at gmx.de
Sat Apr 10 20:35:37 UTC 2010

On 4/10/2010 12:28 PM, stephane ducasse wrote:
> the problem with always loading the latest is that you end up having difficulty
> to load a given version of the past. Here you have only a limited of source entities to sync
> but as soon as you waht to have a couple of package it does not really scale.

That's why David said "in general". Yes, we're aware of that. It's why 
we've always had file releases. If you want to rebuild precisely some 
version of the VM you fetch the appropriate file release.

> This is why metacello is good like that we could in 3 years from now build again
> a system for 1.0.

Metacello does not help with that. What David was pointing out that if 
people pull from head, then they need to do it consistently. Assuming 
that a head version of SVN works with an old version that someone stuck 
into Metacello is futile.

   - Andreas

>> On Sat, Apr 10, 2010 at 08:03:41AM +0200, laurent laffont wrote:
>>> I've used ConfigurationOfVMMaker  1.2 but after I've updated VMMaker package
>>> only. trunk doesn't compile with VMMaker-dtl.157. Maybe it's time for
>>> version ConfigurationOfVMMaker 1.3 ?
>> In general, if you are building a VM with the latest version of platform
>> code from Subversion, then you would also want to use the latest version
>> of VMMaker from SqueakSource. I am not very familiar with Metacello
>> configurations, but I would say that it either needs an update to 1.3,
>> or better would be to just have Metacello always use the latest version.
>> Is there a way to do that?
>> Dave

More information about the Vm-dev mailing list