I have been putting pharo under /usr/local/pharo with bin/ and image/ under that. bin/ contains vm.sh and vm-ui.sh (when using, I think it would be better to have vm.sh only and vm.sh -ui as an option instead of two files. Also, vm.sh isn't too cool a name and I made aliases: alias pharo='/usr/local/pharo/bin/vm-ui.sh' alias pharo14='/usr/local/pharo/bin/vm-ui.sh /usr/local/pharo/image/14/Pharo-1.4.image' alias pharo20='/usr/local/pharo/bin/vm-ui.sh /usr/local/pharo/image/20/Pharo.image' alias pharocli='/usr/local/pharo/bin/vm.sh' in image/, there are 14/ and 20/ where I put the images accordingly as you can see in the aliases. The image/ folder is all read only. That"s one step further for a kind of apt-get packaging :) Phil 2013/3/24 Esteban A. Maringolo <emaringolo@gmail.com>:
2013/3/23 Marcus Denker <marcus.denker@inria.fr>:
Yes, this is why we are going away from the One-Click concept.
The idea is that you install "Pharo2" or "Pharo3" or "Pharo4" on you system, like any Application.
This means for windows, there will be an installer, for Mac it might be in the App Store even.
This Pharo Application is the VM and *read only* image. When you start Pharo it will open this image and ask you to save it to your home dir.
Great!
That is what Dolphin Smalltalk has been doing since version 4, it installs to the shared location, and in the first run it copies the image to your documents folder (by default).
Although I'm ok with "portable" way of doing it, it is better to be able to have the executable in a common location. That will enable Windows users to download "pharo" (and then predefined VM's), or run stuff like "apt-get install pharo-vm"
Regards!