> On 15 Mar 2018, at 09:34, Marcus Denker <[email protected]> wrote: > > > >> On 15 Mar 2018, at 09:27, Esteban Lorenzano <[email protected] >> <mailto:[email protected]>> wrote: >> >> >> >>> On 15 Mar 2018, at 00:08, Cyril Ferlicot <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>> On mer. 14 mars 2018 at 18:18, Marcus Denker <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> >>> > On 9 Mar 2018, at 23:34, Torsten Bergmann <[email protected] >>> > <mailto:[email protected]>> wrote: >>> > >>> > Additional portable versions would be nice too (based on a simple ZIP) >>> > instead of only the installable apps >>> > >>> >>> Is there a deeper reason for this? If I look at “other systems”, they >>> manage to have *one* download, *one* way of installing. >>> For me, offering *a lot* of possible different ways means that the user has >>> to choose without knowing why there is even the option to choose… >>> >>> The problem is that Pharo is different from other systems. When you install >>> eclipse, you'll use the installed eclipse for all your projects for a long >>> time. >>> >>> Pharo images are more like a "disposable". You'll not use the same Pharo >>> image for multiple big projects and you'll more easily throw away an image >>> to take a new one from time to time. >>> >>> Actually I think I download and delete around 5 images/day sometime. >> >> IMO this just strengthen Marcus argument :) >> >>> This complicate a little things because sometime you want to directly >>> download one image. Sometime you want to have one application to manage >>> your images (Pharo launcher) >> >> Why? You have launcher: you download all images you want (btw… I still >> believe launcher UI needs love, but one thing at a time ;) ) >> And if you need more complex stuff, you always have the “other” section. >> >> but I side with Marcus here: we need ONE blessed way of manage pharo, >> otherwise is an un-managable mess. >> >> cheers, >> Esteban >> >> ps: btw, we’ll need also >> - OBS for the launcher (to have linux packaging) >> - signing the launcher on mac (we already did this for the VM, we can do the >> same for launcher). And distribute it as dmg, not zip (a dmg is just a zip >> renamed so no problem here). >> - a windows installer >> > and I would love support for this: https://sparkle-project.org > <https://sparkle-project.org/> to keep the “Pharo” app always up-to-date
dreams, dreams… maybe next year I will have time to do some of this? who knows… > . > > Marcus
