I'm afraid i've got rather lost in this thread.
>> �As an after thought after seeing other posts on the issue, I think
>> �more �than �a �generic �warning �that "may �break �the �image" �the
>> �Monticello comments and/or a �simple explanation on the reasons and
>> �affected �packages *before* �the update �starts with �an �option to
>> �proceed or abort is much in need.
>>
>>
>> �Yes, maybe. �Then thing �is that I �am not �sure in which �cases it
>> would break. Only �in overrides? How many overrides �do we have from
>> external pacakges in Core stuff? �I have no idea.
>
I think given that we are at a very early stage of building the Pharo
image from PharoCore i.e Metacello just coming on etc, we should
simplify the concerns above.
Basically we should only build Pharo on top of a known PharoCore. Just
because packages don't contain overrides does not imply that moving
the core image will break packages on top. Don't offer such a feature,
and then worry about what will happen.
Part of the Pharo build script should set a flag that prevents system
update in the short term.
Ok....it seems all agree more or less in disable it. I like when we take decisions :)
Now...can someone help me with this? It takes too much time to build the images, and congs, etc...
I would appreciate if someone can do it and let me know how to call it from the build script.
I think it should be in Utilities >> updateFromServer
But it would be cool to disable from the menu also. Or maybe, let the menu but bring a popup explaining that it is disable, and why it is.
I opened:�
http://code.google.com/p/pharo/issues/detail?id=1779It would be really cool to have this done before the next dev image :)
Thanks
Mariano