> Am 25.03.2015 um 19:45 schrieb Damien Cassou <[email protected]>: > > In my opinion, the most important thing for you to do is to setup a > continuous integration server. Then you can download ready made, up to date, > and tested images every morning. You can download these images either with or > without the launcher. > Thanks for the input. I'll may try that for other projects. I have a CI server for all of my projects. I need to load a lot of projects into one image in order to maintain changes among them. And I have adjustments to do for every image that are not done on the CI. You might argue that I could make configurations and scripts for all of these. Yes I could but I didn't. The next point is that I develop with pharo4 but the product needs to run on pharo3. So yes I could also build it for pharo3 and pharo4. I also have some workspaces with code snippets I need frequently. This I could script as well. Maybe I'll do all of this. At the moment I just want to update to have an actual pharo and test it and may give feedback. As it is not possible and the change of an image is a burden to me I just do not update. That's all. > If you want to try the launcher, you could symlink the launcher's managed > images from each of your project directories. > That wouldn't work. I save my image often under a different image name because I tend to break the image or it crashes. With the changes log not working the only feasible way is to make a lot of copies of your images. So symlinking is not working that way.
thanks anyway, Norbert > On Mar 24, 2015 3:37 PM, "Norbert Hartl" <[email protected] > <mailto:[email protected]>> wrote: > > > Am 24.03.2015 um 12:41 schrieb Serge Stinckwich <[email protected] > > <mailto:[email protected]>>: > > > > PharoLauncher manage all your images and dl new images directly from the CI > > server. PharoLauncher is written in Pharo and can be adapted to your own > > needs ;-) > > > So there is nothing to gain. My use cases are completely different. I don't > want my images to be managen in one place. I have a lot of projects that have > their own project folder where they live with other resources and they are > organized in a directory structure that makes sense. > My point was preventing the installation of my stuff in a new image > everytime. One project is a lot of stuff to load and adjust and for that I'd > like to just update the image. So to me it appears PharoLauncher is just able > to make my situation worse :) > > Norbert > > > > > Sent from my iPhone > > > >> On 24 mars 2015, at 12:38, Norbert Hartl <[email protected] > >> <mailto:[email protected]>> wrote: > >> > >> What would be better using PharoLauncher? > >> > >> Norbert > >> > >>> Am 24.03.2015 um 12:30 schrieb Serge Stinckwich > >>> <[email protected] <mailto:[email protected]>>: > >>> > >>> Don't update use PharoLauncher instead ! I use PharoLauncher everyday for > >>> my work and I download new images every 2-3 days. > >>> > >>> Sent from my iPhone > >>> > >>>> On 24 mars 2015, at 11:13, Norbert Hartl <[email protected] > >>>> <mailto:[email protected]>> 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 > >> > >> > > > >
