2017-09-15 13:44 GMT+02:00 Denis Kudriashov <[email protected]>: > > 2017-09-15 11:31 GMT+02:00 Guillermo Polito <[email protected]>: > >> Actually, in latest bootstrapped images, images are shipped with sources >> instead of changes. So, as before you had a changes file per image, now you >> have a sources file per image. So there is no really an extra overhead... >> > > Cool. But changes mechanism is still in image? At what point changes are > created? > > And did we plan to remove old changes in Pharo 7? ( Epices is working fine > now) >
when the image is is bootstrapped, it does have no sources nor changes file. But as soon as you start to load packages into it using compiler, all loaded sources are placed in the changes file. When everything is loaded, we condense changes to the sources file so you have all sources in the changes file and empty sources ready for changes done by the image user. -- Pavel >> On Thu, Sep 14, 2017 at 8:57 PM, Pavel Krivanek <[email protected] >> > wrote: >> >>> >>> >>> 2017-09-14 15:10 GMT+02:00 stephan <[email protected]>: >>> >>>> On 14-09-17 14:52, Peter Uhnák wrote: >>>> >>>>> That's not related to Pharo Launcher. Pharo 7 sources (for alpha >>>>> images) are now shipped with the image, not the VM. >>>>> >>>> >>>> That's an issue. I have hundreds of images, and definitely don't need >>>> so many different sources. >>> >>> >>> You can share sources for as many images as you want as soon these >>> images are based on the same bootstrapped image build. >>> >>> -- Pavel >>> >>> >>> >>>> >>>> >>>> Stephan >>>> >>>> >>>> >>> >> >> >> -- >> >> >> >> Guille Polito >> >> >> Research Engineer >> >> French National Center for Scientific Research - *http://www.cnrs.fr* >> <http://www.cnrs.fr> >> >> >> >> *Web:* *http://guillep.github.io* <http://guillep.github.io> >> >> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >> > >
