> I was just thinking if this really makes sense or not...Suppose I have the
> PharoCore image 12121.
>
> From that image, I can shrink it and generate PharoKernel 12121.
>
> If I then have a configuration to load the core again, I will have again
> PharoCore 12121, which I already have, and which I can directly use.
> So...what is the sense of creating again PharoCore from PharoKernel?
>
> A different story is if PharoCore 12121 DOES NOT exist before...so you start
> from PharoKernel 12121 and THEN create PharoCore....but PharoKernel is a
> shrink from PharoCore...soo...?
>
> I am confused :(
>
> cheers
>
> mariano
>
>
> So ...
listen little jedi
- if we do not have an infrastructure in place to manage lot of packages then
there is no need to push to get a little core.
- I would be already really happy if I can take pharoKernel + MCloader ->
loading metacello and loading all the packages and get 12121
- Now when we are in step 2 we will be able to
- cut packages change the map and snap out fingers or think about the
forces and produce better packaged system
- iterate
- I'm not a big believer of shrinking and I would like to have a bootstrap but
this is the path to go.
so ideally at the end of the process we should be able to even recreate
bootstrappedpharoKernel from itself of another image.
Stef
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
