I think we can do it manually, yes. But it would be good to have a detailed description of the manual steps so that we (or someone else) is able to reproduce it at a later point in time. Adrian On Mar 31, 2009, at 16:52 , Marcus Denker wrote:
Hi,
So this is not done as an update... reason: much simpler. doing the closure conversation is a bit manual, e.g. closing all windows, doing some other stuff, then save, restart, cleanup changeset... then re-saving all the dirty packages.
I would *a lot* of work to do that with the update-stream.
The question is: can we live without?
We could add a changeset that just pops up a window that says: end-of- line, please get the hand-build image.
Marcus
On 31.03.2009, at 16:15, Marcus Denker wrote:
Hi,
I have merged the closure changed in the 1062 image (manually).
We now can continue with this image to provide updates using the update stream:
http://gforge.inria.fr/frs/download.php/20098/ Pharo0.1Core-10262cl.zip
Changes: -> Closure changes merged. -> BlockClosurePharo.1.cs -> FixDebugger.1.cs -> TraitDescription-closure support.st -> BlockContextTestFix.1.cs -> ArrayLiteralTestFix.1.cs
-- Marcus Denker -- denker@acm.org http://www.marcusdenker.de
-- Marcus Denker -- denker@acm.org http://www.marcusdenker.de
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project