@Norbert: I also use PharoLauncher, this way I can download clean 3.0/4.0 or prepackaged (Moose, Boostrap) images at own will, clone, copy as I like and with a fresh image it is easy to see if code is loading cleanly, ...
I have to give up nothing. I can still profit from image development as I can save my image as usual and continue with it later. @Kilon: Integrating PharoLauncher in the standard image would not make sense. Then I use PharoLauncher to download an image with a prepackaged PharoLauncher, ... If you mean that it should be the default tool to download when getting Pharo 4.0 or Pharo 3.0 from the download page or from zeroconf then I would agree. Maybe some more help is needed for Pharo newbees then. But I would vote for it as I would download/install Pharo one time on a machine and then choose - download - start the image that I like. Gesendet: Dienstag, 24. März 2015 um 11:25 Uhr Von: "kilon alios" <kilon.al...@gmail.com> An: "Pharo Development List" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] Update question I tried it a few times, and had nothing but problems with it. We have discussed here several times and from what I have learned there several technical limitation. I am using pharolauncher non stop and wonder why Pharolauncher is not integrated inside Pharo yet. I have added my code inside the configuration browser (Ephestos, Nireas) and Installing my code back in a fresh image is just a two click process. On Tue, Mar 24, 2015 at 12:13 PM, Norbert Hartl <norb...@hartl.name> wrote:Today I wanted (again) to update my image and it can't find GT packages. So I'm interested how the community deals with that. Do you take fresh downloaded images regularly? Or you do not update? Is it just me? thanks, Norbert
