It is better to use smaller bootstrapped image without Monticello but it is still quite big.
https://ci.inria.fr/pharo/view/6.0-SysConf/job/Pharo-6.0-Step-01-00-Bootstrap/lastSuccessfulBuild/artifact/bootstrap.zip -- Pavel 2016-12-30 18:13 GMT+01:00 Ben Coman <[email protected]>: > On Fri, Dec 30, 2016 at 7:51 AM, James Ladd <[email protected]> wrote: > > Hi Pharo People, > > > > I have continued work on Redline Smalltalk and I'm wanting to discuss > what > > the absolute minimum > > set of Classes and method should be included in the Redline Runtime. > > > > Would anyone here like to participate in that discussion? > > > > - James. > > Redline Smalltalk <http://redline.st> > > Nice to hear you are continuing. > I'm not very knowledgable on this, but I'll show you how to pull some > data from the work on producing a minimal image. > > 1. From PharoLauncher > Templates > Pharo 6.0(beta) > download/create an image of build "60334-minimal". > 2. Right-click on the image and choose [Copy pathname] > 3. In a shell, change to that directory, and execute the following > $ ../../VMs/spur/pharo 60334-minimal.image eval "Object allSubclasses > size" > ==> 2801 > $ ../../VMs/spur/pharo 60334-minimal.image eval "Object class > allSubclasses size" > ==> 1399. > $ ../../VMs/spur/pharo 60334-minimal.image eval "Object class > printHierarchy" > /tmp/60334-minimal-class-hierarchy.txt > > I've attached the output of that last one. > > 4. For comparison, in a standard 60334 image, > Object allSubclasses size "==>11923". > Object class allSubclasses size "==>5959". > > Now in Pharo 6, the minimal image starts with a standard image and > strips these things out... > https://ci.inria.fr/pharo/job/Pharo-6.0-Update-Step-3.2- > Minimal/ws/output.txt > > In Pharo 7, there will be a new build system that it will start with a > minimal image and build it up to a normal image. So this may provide > a better way to understand the order that things need to be > implemented. > > cheers -ben >
