23 May
2011
23 May
'11
11:51 p.m.
I think both Stef and Lukas are right.
Yes configuration management is crucial to be able to evolve and manage the dependencies.
But Metacello does not seem to offer the right trade-offs between the effort of setting up
/ maintaining configurations and the 'guarantees' of being able to load
old/specific versions of X .
The latter is my interpretation of lukas' point, colored by my recent explorations
with confgurations. Please forgive me if I am wrong.
I wish I had an answer to the problem, but I dont, sorry :-(
On 23 May 2011, at 17:14, Stéphane Ducasse wrote:
Lukas
If doru specifies that you always load the lastest bleeding edge then how the system
would magically know what do load when you go back to use
an old image? Tell me because I'm curious to know.
Now I can take my configuration and load them in old versions without problems.
Now with the symbolic version this is even simpler.
Then finally without configurations to manage complex dependencies there is no way that
we will scale and not end up
in a group of guys having fun with our old little image. If we cannot control what is
loadable together, then better stop
to try to build a better smalltalk. Especially at the speed of change we are.
Stef
On May 23, 2011, at 10:26 PM, Lukas Renggli wrote:
> I notice this problem too. It left me puzzled why we have to deal with
> all these configurations if we then can't even load an old version? I
> always thought that it was one of the main arguments of Metacello to
> have a specification that we can use to load old versions in 10 years
> from now :-/
>
> Lukas
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile