Hi Torsten, we plan to do that in Pharo/SystemConfigurations(/Unreloader). That mail was something like a late night backup of very experimental stuff :-) Cheers, -- Pavel 2014-03-19 9:08 GMT+01:00 Torsten Bergmann <astares@gmx.de>:

Hi Pavel,

dont know if this is a good idea but why not: - put this into a ConfigurationOfNoTools with a spec postLoadDoIt: #postloadToShrinkWithLoader:package:. - put the script into a #postloadToShrinkWithLoader:package - store the project on STHub - create a CI job for loading the Config

This way one can: - browse the changes to the script in Monticello as it progresses - have the CI built the image automagically - the final image can be downloaded from CI or using Pharo launcher easily

If some simply unit tests will be applied (like checking for Undeclared, etc) one can control if the image will get/be/stay red or green.

Bye T.

*Gesendet:* Dienstag, 18. März 2014 um 23:00 Uhr *Von:* "Pavel Krivanek" <pavel.krivanek@gmail.com> *An:* "Discusses Development of Pharo" <pharo-dev@lists.pharo.org> *Betreff:* [Pharo-dev] Removing tools Hi,

this is an initial attempt to produce an image without development tools. Currently it leaves Workspace and Transcript in the image, has no obsolete classes and six Undeclared. The image size is still quite big, 16.1 MB. Tested on #30798. Do not forget to share your improvements ;-)

Cheers, -- Pavel