On Sat, Oct 7, 2017 at 3:38 PM, Nicolai Hess <nicolaihess@gmail.com> wrote:

Just starting pharolauncher on windows still does not work (if you put it into the default "program" folder).
On start, it tries to create a local direcitory "pharo-local" and does not have the permission to do so.
You need to start it with admin-rights.

Why are we making it harder for Windows users in corporate environments by requiring them to have admin-rights they often won't have, while in Linux PharoLancher is installed into user folders?

Also there is the��UAC Virtualization fiasco that complicates installing upgrades.

http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2014-January/091645.html

Could we *please* install Windows PharoLauncher into user folders?
What reason is there not to?

cheers -ben

��

On Fri, Oct 6, 2017 at 5:35 PM, Christophe Demarey <christophe.demarey@inria.fr> wrote:
Hi Gabriel,

Le 6 oct. 2017 �� 15:48, Gabriel Cotelli <g.cotelli@gmail.com> a ��crit :

I've tried it on Linux, and after the download has finished it cannot launch a Pharo 6.1 image. Find attached the PharoDebug.log

Seems it's searching for the sources file in a wrong location.
Pharo cannot locate the sources file named /home/gcotelli/Pharo/pharo-launcher/bin/lib/pharo/5.0-201707201942/PharoV60.sources.

I have wondered for a while if sources files should searched for up the directory hierarchy looking for a "/sources" folder to minimize the number of copies needed.

cheers -ben