On 27 Jan 2014, at 14:49, Norbert Hartl <[email protected]> wrote:
> Very cool,
>
> it would be very good if the ImageCleaner would enable me to manage what
> needs to be cleaned. At the moment it is all or nothing. My use case is that
> I like SUnit to stay in the image. I’m not only writing module tests while
> developing but also runtime test cases that monitor the health of the image.
> It would be wonderful having an easy way to take control of that process.
> Just an idea for those who have a enough time and no current project to deal
> with :)
>
yes… it’s a very ad hoc thing. #cleanUpForProduction needs more work anyway, as
lots of packages are dirty after.
One of the things that should be changed is to *not* unload SUnit. The time
when that was useful is over… people like to run tests in deployment more than
conserve memory.
But in general, this is all very very hackish anyway and what we need it a
Pharo that is bootstrapped from a description…
Marcus
