> Am 24.03.2015 um 12:41 schrieb Serge Stinckwich <[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]> wrote: >> >> What would be better using PharoLauncher? >> >> Norbert >> >>> Am 24.03.2015 um 12:30 schrieb Serge Stinckwich >>> <[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]> 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 >> >> >
