Here is the job: https://ci.inria.fr/pharo-contribution/view/Pharo-Kernel-3.0/job/PharoKernel3.0-FromTopShrink/
-- Pavel 2014/1/20 Sven Van Caekenberghe <[email protected]> > > On 19 Jan 2014, at 09:44, Pavel Krivanek <[email protected]> wrote: > > > > > 2014/1/18 Sven Van Caekenberghe <[email protected]> > > > > On 18 Jan 2014, at 20:53, Benjamin <[email protected]> > wrote: > > > > > COOOOOOOLLLLLLL !!!!!! > > > > +1 > > > > And interesting as well (I want to understand how to unload NB, for > example). > > > > For simplicity I use the attached code. The image needs to be restarted > after NB unloading. To do it properly, we need to solve this issues: > > > https://pharo.fogbugz.com/f/cases/12624/make-image-startup-independent-on-NativeBoost > > > https://pharo.fogbugz.com/f/cases/11869/NativeBoost-usage-in-PreferenceStartup-raises-an-exception-on-StackVM > > > > -- Pavel > > > > > > > > > Ben > > > > > > On 18 Jan 2014, at 16:37, Pavel Krivanek <[email protected]> > wrote: > > > > > >> Hi, > > >> > > >> I finally successfully created a script that is able to unload > everything *by Monticello* except kernel packages, network, Monticello, > Gofer and related packages. I will setup a job when Jenkins will be healthy > again. > > >> It uses several temporary patches that we need to solve properly: > > >> - make NativeBoost optional > > >> - make UserManager optional > > >> - small super-easy issue > https://pharo.fogbugz.com/f/cases/12679/change-package-of-ClassTrait-soleInstance > > >> > > >> The size of resultant image is about 6.6 MB, 4.9 MB without MC data > and caches. BTW in the full image Monticello data have about 5MB. The image > has no Undeclared nor obsolete classes and is really able to load something > using Gofer. > > >> > > >> With some care we can make it usable base for the next > remodularization effort. > > >> > > >> Cheers, > > >> -- Pavel > > >> > > > > > > > > > > > <cleanAfterNB.st><unloadNB.st> > > Thanks for the scripts, Pavel. > > I was already looking at the environment stuff, it is good to see that the > problem is confined to that area. > > When I continue trying to make a 3.0 image run on the Raspberry Pi, I will > try using this script. > > Sven > > >
