On 15 Apr 2013, at 15:54, "Sean P. DeNigris" <sean@clipperadams.com> wrote:
Sven Van Caekenberghe-2 wrote
The test.image contains all your project specific code, and loading the config just checks all dependencies and only loads what has changed, incrementally. It only takes some 10s of seconds.
It never occurred to me that this was the way to go, but the config handler does it by default. Maybe it is just me, but I had the impression that everybody (including CIs) always built from scratch (more or less, there were staged systems), while it is actually quite practical to keep on updating the same image for a much faster turn around.
Ah, I see. The speed is very nice, but what about e.g. class-side initialization? i.e. if a class>>initialize has changed, the update will not be run, no.
Yes it will, if you change the source code of the #initialize that you want to force run, else you have to add post load actions to the metacello configs, or call some initializers manually from you startup scripts. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org