Hilaire I like your goal because this is what we want to achieve. what you should know is that the Pharo packages that we load to create Pharo are not all modular because they were not. We started to get Pharo modular and we will continue. On two fronts: - getting the core smaller - getting pharo more modular So if you see - packages where a dependency can be easily removed (for example by producing two packages instead of one). - packages that can just be loaded separately (we could just create a new package out an larger one). - packages that can just be thrown away. let us know. Stef On Sat, Jun 24, 2017 at 10:29 AM, Hilaire <hilaire@drgeo.eu> wrote:
Hi Pavel,
Le 24/06/2017 à 09:35, Pavel Krivanek a écrit :
The question is what is your goal because the bootstrapped image will
I want to build an image for DrGeo which is not 60MB. (the size I have now on my P6 dev image for Dr. Geo)
Until now, DrGeo was installed then unecessary packages removed. With the first Pharo release, DrGeo image was around 10MB, in the latest DrGeo release (based on P3), its image is more than 20MB.
For P6, if possible, I would like to use the bootstrap process
have in the end (almost) the same content as the default non-bootstrapped image. You probably want to change the content of the produced image wich requires to modify the related baselines and do not load them all. For Dr Geo you will probably want to start with the BaselineOfMorphic however you will probably need a lot of custom modifications.
I don't know... May be we can take Dr. Geo as an excuse to see step by step how to do it. If we succeed I could document it so it may be useful to other.
-- Dr. Geo http://drgeo.eu