[Pharo-project] Power of Fuel - Pharo-Kernel to Pharo-Core in 15 seconds
Hi, I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes. Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes. If anyone will want, I send him an archive with the images and ad-hoc fixes. Cheers, -- Pavel
You can see it in action: http://www.youtube.com/watch?v=pOyvXamn3Y4 -- Pavel On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes.
Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes.
If anyone will want, I send him an archive with the images and ad-hoc fixes.
Cheers, -- Pavel
wow :) On Apr 10, 2012, at 2:48 PM, Pavel Krivanek wrote:
You can see it in action: http://www.youtube.com/watch?v=pOyvXamn3Y4
-- Pavel
On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes.
Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes.
If anyone will want, I send him an archive with the images and ad-hoc fixes.
Cheers, -- Pavel
On 10 Apr 2012, at 14:52, Esteban Lorenzano wrote:
wow :)
+111
On Apr 10, 2012, at 2:48 PM, Pavel Krivanek wrote:
You can see it in action: http://www.youtube.com/watch?v=pOyvXamn3Y4
-- Pavel
On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes.
Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes.
If anyone will want, I send him an archive with the images and ad-hoc fixes.
Cheers, -- Pavel
nice :) Doru On Tue, Apr 10, 2012 at 3:28 PM, Sven Van Caekenberghe <sven@beta9.be> wrote:
On 10 Apr 2012, at 14:52, Esteban Lorenzano wrote:
wow :)
+111
On Apr 10, 2012, at 2:48 PM, Pavel Krivanek wrote:
You can see it in action: http://www.youtube.com/watch?v=pOyvXamn3Y4
-- Pavel
On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes.
Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes.
If anyone will want, I send him an archive with the images and ad-hoc fixes.
Cheers, -- Pavel
-- www.tudorgirba.com "Every thing has its own flow"
On 4/10/12 9:48 AM, "Pavel Krivanek" <pavel.krivanek@gmail.com> wrote:
You can see it in action: http://www.youtube.com/watch?v=pOyvXamn3Y4
-- Pavel
On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes.
Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes.
If anyone will want, I send him an archive with the images and ad-hoc fixes.
Cheers, -- Pavel
Extraordinario !!! When MinimalMorphic (or newer concept) in Pharo with Fuel ? Edgar
On Tue, Apr 10, 2012 at 3:31 PM, Edgar J. De Cleene <edgardec2005@gmail.com> wrote:
On 4/10/12 9:48 AM, "Pavel Krivanek" <pavel.krivanek@gmail.com> wrote:
You can see it in action: http://www.youtube.com/watch?v=pOyvXamn3Y4
-- Pavel
On Tue, Apr 10, 2012 at 12:41 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi,
I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes.
Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes.
If anyone will want, I send him an archive with the images and ad-hoc fixes.
Cheers, -- Pavel
Extraordinario !!! When MinimalMorphic (or newer concept) in Pharo with Fuel ?
Edgar
With start of 1.5 we plan to integrate Fuel and split Morphic packages. Then the show will begin :-) -- Pavel
On 4/10/12 10:38 AM, "Pavel Krivanek" <pavel.krivanek@gmail.com> wrote:
With start of 1.5 we plan to integrate Fuel and split Morphic packages. Then the show will begin :-)
-- Pavel
Yes, I want first row ticket !! And congrats Pavel
Great! :D Thanks Pavel, we have to work on these issues. I reported them in http://code.google.com/p/fuel/issues/detail?id=143 It would be very nice to be full-time for the project during the Winter (propaganda for my Google Summer of Code proposal ;) I'm on the Southern hemisphere!) BTW, we should find a better name than FuelPackageLoader! Cheers MartÃn On Tue, Apr 10, 2012 at 10:49 AM, Edgar J. De Cleene <edgardec2005@gmail.com
wrote:
On 4/10/12 10:38 AM, "Pavel Krivanek" <pavel.krivanek@gmail.com> wrote:
With start of 1.5 we plan to integrate Fuel and split Morphic packages. Then the show will begin :-)
-- Pavel
Yes, I want first row ticket !!
And congrats
Pavel
On Tue, Apr 10, 2012 at 5:00 PM, Martin Dias <tinchodias@gmail.com> wrote:
Great! :D
Thanks Pavel, we have to work on these issues. I reported them in http://code.google.com/p/fuel/issues/detail?id=143
It would be very nice to be full-time for the project during the Winter (propaganda for my Google Summer of Code proposal ;) I'm on the Southern hemisphere!)
Me too. At least this Saturday I finish the paper so I will have some time for Fuel. Thanks Pavel for your work. It is nice to see people doing cool stuff on top of Fuel. That was the idea. I meantioned it in the talk at ESUG: Fuel is not a plain serializer, it is a behicule you can use or even on which you can build things on top.
BTW, we should find a better name than FuelPackageLoader!
I told you one ;) but you didn't like it: Barrel
Cheers MartÃn
On Tue, Apr 10, 2012 at 10:49 AM, Edgar J. De Cleene < edgardec2005@gmail.com> wrote:
On 4/10/12 10:38 AM, "Pavel Krivanek" <pavel.krivanek@gmail.com> wrote:
With start of 1.5 we plan to integrate Fuel and split Morphic packages. Then the show will begin :-)
-- Pavel
Yes, I want first row ticket !!
And congrats
Pavel
-- Mariano http://marianopeck.wordpress.com
Thanks Pavel for your work. It is nice to see people doing cool stuff on top of Fuel. That was the idea. I meantioned it in the talk at ESUG: Fuel is not a plain serializer, it is a behicule you can use or even on which you can build things on top.
BTW, we should find a better name than FuelPackageLoader!
I told you one ;) but you didn't like it: Barrel
If it helps Fuel with the Loading, then it's a Pump! (or Pampa if you want to play with words and make it sound argentinian)
BTW, we should find a better name than FuelPackageLoader!
I propose Injector
Excellent name! ("Fuel injection" is a common automotive term in English.) -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
On 4/11/12 2:22 PM, "Craig Latta" <craig@netjam.org> wrote:
Excellent name! ("Fuel injection" is a common automotive term in English.)
And as Formula One fan is why the proposal. Muy bien diez para Mariano, Martin, etc :=) Edgar
On Wed, Apr 11, 2012 at 2:22 PM, Craig Latta <craig@netjam.org> wrote:
BTW, we should find a better name than FuelPackageLoader!
I propose Injector
Excellent name! ("Fuel injection" is a common automotive term in English.)
:) good names! Well, I like Pump, but I vote for Injector also. Pampa is already used by Fernando Olivero in Gaucho ;) Barrel should be a candidate for the "fuel package", i.e. the file with the classes, traits, extension methods, timestamps, etc. inside. We have to think a name for this element also! Some synonyms / related words taken from the dictionary: barrel cask keg tub tun tin capsule nitro people choice?
-C
-- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
+1 Barrel :) On 12 Apr 2012, at 03:52, Martin Dias wrote:
On Wed, Apr 11, 2012 at 2:22 PM, Craig Latta <craig@netjam.org> wrote:
BTW, we should find a better name than FuelPackageLoader!
I propose Injector
Excellent name! ("Fuel injection" is a common automotive term in English.)
:) good names!
Well, I like Pump, but I vote for Injector also.
Pampa is already used by Fernando Olivero in Gaucho ;)
Barrel should be a candidate for the "fuel package", i.e. the file with the classes, traits, extension methods, timestamps, etc. inside. We have to think a name for this element also! Some synonyms / related words taken from the dictionary:
barrel cask keg tub tun tin capsule nitro
people choice?
-C
-- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
On Thu, Apr 12, 2012 at 4:52 AM, Martin Dias <tinchodias@gmail.com> wrote:
On Wed, Apr 11, 2012 at 2:22 PM, Craig Latta <craig@netjam.org> wrote:
BTW, we should find a better name than FuelPackageLoader!
I propose Injector
Excellent name! ("Fuel injection" is a common automotive term in English.)
:) good names!
Well, I like Pump, but I vote for Injector also.
Pampa is already used by Fernando Olivero in Gaucho ;)
Barrel should be a candidate for the "fuel package", i.e. the file with the classes, traits, extension methods, timestamps, etc. inside. We have to think a name for this element also! Some synonyms / related words taken from the dictionary:
Exactly. I like having a name for the "fuel package", as you said, the file with the classes, the code, etc etc. So then you can say "download the barrel of Seaside". This is what parcels does. At we can even have files .barrel. Now...should this be the same name as the framwork itself? (FuelPackageLoader) ? Don't know...in Parcels it is.. I mean, parcels is both, the frameowrk and the file. For the framework I like Injector :) well..now Esteban recommends: FuelInjector load: 'Seaside30.nitro' hehehehe
barrel cask keg tub tun tin capsule nitro
people choice?
-C
-- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
-- Mariano http://marianopeck.wordpress.com
Martin Dias wrote:
On Wed, Apr 11, 2012 at 2:22 PM, Craig Latta <craig@netjam.org> wrote:
BTW, we should find a better name than FuelPackageLoader!
I propose Injector
Excellent name! ("Fuel injection" is a common automotive term in English.)
:) good names!
Well, I like Pump, but I vote for Injector also.
Pampa is already used by Fernando Olivero in Gaucho ;)
Barrel should be a candidate for the "fuel package", i.e. the file with the classes, traits, extension methods, timestamps, etc. inside. We have to think a name for this element also! Some synonyms / related words taken from the dictionary:
barrel cask keg tub tun tin capsule nitro
people choice?
-C
-- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
+1 Injector - it aligns well with the task of injecting a package into the image. More than those other options, a fuel-can or fuel-tank is where you keep your fuel - but sometimes you can stretch an analogy too far.
so let use Injector! for the package, we have: barrel can tank nitro keg Ok... probably I should go to sleep now instead of saying the following, but... a tank can be a repository for nitros! On Thu, Apr 12, 2012 at 8:46 AM, Ben Coman <btc@openinworld.com> wrote:
Martin Dias wrote:
On Wed, Apr 11, 2012 at 2:22 PM, Craig Latta <craig@netjam.org> wrote:
BTW, we should find a better name than FuelPackageLoader!
I propose Injector
Excellent name! ("Fuel injection" is a common automotive term in English.)
:) good names!
Well, I like Pump, but I vote for Injector also.
Pampa is already used by Fernando Olivero in Gaucho ;)
Barrel should be a candidate for the "fuel package", i.e. the file with the classes, traits, extension methods, timestamps, etc. inside. We have to think a name for this element also! Some synonyms / related words taken from the dictionary:
barrel cask keg tub tun tin capsule nitro
people choice?
-C
-- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
+1 Injector - it aligns well with the task of injecting a package into the image. More than those other options, a fuel-can or fuel-tank is where you keep your fuel - but sometimes you can stretch an analogy too far.
Nice job! I also want a first row ticket, near Edgar! 2012/4/10 Edgar J. De Cleene <edgardec2005@gmail.com>
On 4/10/12 10:38 AM, "Pavel Krivanek" <pavel.krivanek@gmail.com> wrote:
With start of 1.5 we plan to integrate Fuel and split Morphic packages. Then the show will begin :-)
-- Pavel
Yes, I want first row ticket !!
And congrats
Pavel
I love your attitude: a hammer and systematically beating beating beating the same huge nail until we get thereâ¦. I love that. I call that the bull attitude: I'm like that too :). Stef On Apr 10, 2012, at 12:41 PM, Pavel Krivanek wrote:
Hi,
I tried to load entire Pharo-Core content into Pharo-Kernel with help of Fuel and I was successful. It was done in 4 steps: - load and initialize all packages up to Gofer (gofer.fuel) - load and initialize Ring (ring.fuel) - load rest of the Paharo-Core packages (pharo-core.fuel) - do the initialization of Morphic and the rest of the system. All that takes about 15 seconds on my old laptop. Normally it takes about 12 minutes.
Of course there are several issues we have to solve permanently: - current Fuel cannot load several packages at once but it is very easy to enhance it. - Fuel has some problems with Traits (registerOnLoad, rebindOnLoad, sometimes nil category) - the packages must be clean because Fuel raises error when it uses unknown global variable - Fuel must have a way how to disable initialization of loaded classes - some packages like Morphic have extension methods in categories named "*Morphic-something". PackageInfo ignores it and expects that this categories are extending categories of some different package. - it doesn't store to Changes.
If anyone will want, I send him an archive with the images and ad-hoc fixes.
Cheers, -- Pavel
Hi Pavel-- Can you then unload everything you loaded? thanks, -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
Hi Craig, as I mentioned, Fuel package loader now doesn't store to changes file so the generated image has problems with recompilation and shrinking process doesn't work. However the process that uses Monticello can be shrinked again. You can try it if you will download the latest result of Pharo Kernel Reload job from the CI server: https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Reloa... and evaluate: Smalltalk shrinkToKernel If the resultant image generated by Fuel will be healthy then the shrinking to Kernel should work too without modifications. Cheers, -- Pavel On Wed, Apr 11, 2012 at 7:23 AM, Craig Latta <craig@netjam.org> wrote:
Hi Pavel--
  Can you then unload everything you loaded?
  thanks,
-C
-- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
On Wed, Apr 11, 2012 at 9:46 AM, Pavel Krivanek <pavel.krivanek@gmail.com>wrote:
Hi Craig,
as I mentioned, Fuel package loader now doesn't store to changes file so the generated image has problems with recompilation and shrinking process doesn't work.
Pavel: if you use FLCompiledMethodCluster withSourceCode instead of #withNoTrailerChange then sources are stored in the trailer of the serialized CompiledMethod. Therefore, you can recompile later of if you want. Of course, the serilzalization/materialization will be a little bit slower because you are including sources. Cheers
However the process that uses Monticello can be shrinked again. You can try it if you will download the latest result of Pharo Kernel Reload job from the CI server:
https://ci.lille.inria.fr/pharo/view/Pharo-Kernel/job/Pharo%20Kernel%20Reloa...
and evaluate:
Smalltalk shrinkToKernel
If the resultant image generated by Fuel will be healthy then the shrinking to Kernel should work too without modifications.
Cheers, -- Pavel
On Wed, Apr 11, 2012 at 7:23 AM, Craig Latta <craig@netjam.org> wrote:
Hi Pavel--
Can you then unload everything you loaded?
thanks,
-C
-- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 415 287 3547 + 1 510 282 7468
-- Mariano http://marianopeck.wordpress.com
Hi Mariano, On Wed, Apr 11, 2012 at 11:28 AM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, Apr 11, 2012 at 9:46 AM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi Craig,
as I mentioned, Fuel package loader now doesn't store to changes file so the generated image has problems with recompilation and shrinking process doesn't work.
Pavel: if you use FLCompiledMethodCluster withSourceCode instead of #withNoTrailerChange  then sources are stored in the trailer of the serialized CompiledMethod. Therefore, you can recompile later of if you want. Of course, the serilzalization/materialization will be a little bit slower because you are including sources.
ehhh, I used Fuel from SqueakSource (mentioned in all materials), I didn't know that there is a newever version on ss3.gemstone.com :-) -- Pavel
On Wed, Apr 11, 2012 at 11:52 AM, Pavel Krivanek <pavel.krivanek@gmail.com>wrote:
Hi Mariano,
On Wed, Apr 11, 2012 at 11:28 AM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, Apr 11, 2012 at 9:46 AM, Pavel Krivanek <
pavel.krivanek@gmail.com>
wrote:
Hi Craig,
as I mentioned, Fuel package loader now doesn't store to changes file so the generated image has problems with recompilation and shrinking process doesn't work.
Pavel: if you use FLCompiledMethodCluster withSourceCode instead of #withNoTrailerChange then sources are stored in the trailer of the serialized CompiledMethod. Therefore, you can recompile later of if you want. Of course, the serilzalization/materialization will be a little bit slower because you are including sources.
ehhh, I used Fuel from SqueakSource (mentioned in all materials), I didn't know that there is a newever version on ss3.gemstone.com :-)
ups..yes sorry. In fact, we did not mention it on purpose (to avoid problems). Fuel up to Fuel 1.7 should be in ss. We were going to mention that with the soon release of Fuel 1.8 which will be in ss3. Anyway, I forgot that I added #withSourceCode after 1.7, i.e, in the new repo ;) -- Mariano http://marianopeck.wordpress.com
On Wed, Apr 11, 2012 at 11:55 AM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, Apr 11, 2012 at 11:52 AM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi Mariano,
On Wed, Apr 11, 2012 at 11:28 AM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
On Wed, Apr 11, 2012 at 9:46 AM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
Hi Craig,
as I mentioned, Fuel package loader now doesn't store to changes file so the generated image has problems with recompilation and shrinking process doesn't work.
Pavel: if you use FLCompiledMethodCluster withSourceCode instead of #withNoTrailerChange  then sources are stored in the trailer of the serialized CompiledMethod. Therefore, you can recompile later of if you want. Of course, the serilzalization/materialization will be a little bit slower because you are including sources.
ehhh, I used Fuel from SqueakSource (mentioned in all materials), I didn't know that there is a newever version on ss3.gemstone.com :-)
ups..yes sorry. In fact, we did not mention it on purpose (to avoid problems). Fuel up to Fuel 1.7 should be in ss. We were going to mention that with the soon release of Fuel 1.8 which will be in ss3. Anyway, I forgot that I added #withSourceCode after 1.7, i.e, in the new repo ;)
:-) well, can you give me write permissions (krivanek)? -- Pavel
-- Mariano http://marianopeck.wordpress.com
ups..yes sorry. In fact, we did not mention it on purpose (to avoid problems). Fuel up to Fuel 1.7 should be in ss. We were going to mention that with the soon release of Fuel 1.8 which will be in ss3. Anyway, I forgot that I added #withSourceCode after 1.7, i.e, in the new repo ;)
:-) well, can you give me write permissions (krivanek)?
Done.
-- Pavel
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
On Wed, Apr 11, 2012 at 12:04 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
ups..yes sorry. In fact, we did not mention it on purpose (to avoid problems). Fuel up to Fuel 1.7 should be in ss. We were going to mention that with the soon release of Fuel 1.8 which will be in ss3. Anyway, I forgot that I added #withSourceCode after 1.7, i.e, in the new repo ;)
:-) well, can you give me write permissions (krivanek)?
Done.
Thank you -- Pavel
-- Pavel
-- Mariano http://marianopeck.wordpress.com
-- Mariano http://marianopeck.wordpress.com
participants (13)
-
Ben Coman -
Craig Latta -
Edgar J. De Cleene -
Esteban Lorenzano -
Francisco Garau -
Germán Arduino -
Mariano Martinez Peck -
Mark Smith -
Martin Dias -
Pavel Krivanek -
Stéphane Ducasse -
Sven Van Caekenberghe -
Tudor Girba