> On 4 Mar 2018, at 17:46, Sean P. DeNigris <s...@clipperadams.com> wrote:
>
> Pharo Smalltalk Users mailing list wrote
>> Estaban,
>> I guess there are some advantages to shrink the image (as compared to
>> bootstrapping from a minimal image)
>
> Also, they are not mutually exclusive. While bootstrapping seems a clear
> choice for building images. A tool could then scan an image (e.g. for
> deployment) and pare it down to just what's needed. IIRC Self might have
> done some work in this direction…
>
Pharo7 still has ImageCleaner. It needs some work (even for Pharo6 it would
be nice to do a pass).
Vincent (I think) did already one improvement to it in Pharo7 (simplified test
unloading).
I did find some time to do an experiment with Pharo7, and if you remove all
tests and documentation with ImageCleaner (after a small fix, will commit that),
the image shrinks fro 38 to 35 (I had expected a bit more).
*But*: just opening it and running the “Do Image Cleanup”, then save and quit,
the image is again close to 38MB, which is *very* strange!
So for size there is something strange going on. We need to have a closer look.
I have put on my TODO:
- do a pass on ImageCleaner Pharo6 and Pharo7
- start to find duplicated code to not load anymore in the bootstrap
(e.g.
old compiler, inspector…).
Marcus
