Hi christophe
This is why we worked (but never released) on silent Pharo. Stef On Mon, Oct 9, 2017 at 9:59 AM, Christophe Demarey <[hidden email]> wrote: > > Le 7 oct. 2017 à 14:26, Ben Coman <[hidden email]> a écrit : > > On Sat, Oct 7, 2017 at 3:38 PM, Nicolai Hess <[hidden email]> 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? > > > « Program » folder is the default location where to install apps on Windows. > If a user does not have admin rights, he can simply install it under its > home directory. > > 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? > > > Users can choose to install Pharo Launcher where they wish. > We could choose another default location but not sure it is best option. > > To me, the real problem is: why does Pharo apps (and Pharo Launcher) needs > to write data in the application directory? By example, for Pharo Launcher, > we do not need to load any code nor to backup sessions. |
In reply to this post by Peter Uhnak
Perfectly understandable.
No need to patch, you already have settings to configure where to store images and virtual machines. Regards, Christophe |
In reply to this post by Vitor Medina Cruz
Hi Vitor,
For Windows, Pharo is shipped with an installer. Its only goal is to ask you where to install Pharo. So yes, the installation directory is configurable. Just to be sure, here the link to the installer: http://files.pharo.org/platform/launcher/pharo_installer-1.0.1.exe |
In reply to this post by demarey
On 06-10-17 13:26, Christophe Demarey wrote:
> For those wanted more info on how the adequate VM is computed, here is the process: > determine the image format version > find (and optionnaly fetch) a compatible VM (a VM able to run this image format) and run the image to get its Pharo version number > find (and optionnaly fetch) the appropriate VM for this specific Pharo image version. Sources files are also downloaded with the VM when applicable. > run the image with the appropriate VM Thanks, Christophe. It might be useful to regularly check for newer vms, at least the stable ones. VMs are supposed to be backwards compatible. Stephan |
In reply to this post by demarey
Hi Christophe, Yes, but:1- I can’t execute it if I don’t have administrative rights — I have tried with the provided link. Before I get to the installation directory choice, windows prompt me an error telling me I must be an admin. It is probably some windows policy for all exe files, I know it is possible to bypass this as some applications do (Intellij for example), but it is usually easier to provide a zip; 2- 7-Zip can open this executable as it were a zip file, that’s how I manage to install Pharo Launcher. On Wed, Oct 11, 2017 at 4:17 AM, Christophe Demarey <[hidden email]> wrote:
|
In reply to this post by Stephan Eggermont-3
> Le 11 oct. 2017 à 12:10, stephan <[hidden email]> a écrit : > > On 06-10-17 13:26, Christophe Demarey wrote: >> For those wanted more info on how the adequate VM is computed, here is the process: >> determine the image format version >> find (and optionnaly fetch) a compatible VM (a VM able to run this image format) and run the image to get its Pharo version number >> find (and optionnaly fetch) the appropriate VM for this specific Pharo image version. Sources files are also downloaded with the VM when applicable. >> run the image with the appropriate VM > > Thanks, Christophe. > > It might be useful to regularly check for newer vms, at least the stable ones. VMs are supposed to be backwards compatible. Right. I added an issue: https://github.com/pharo-project/pharo-launcher/issues/42 |
In reply to this post by demarey
On Wed, Oct 11, 2017 at 3:17 PM, Christophe Demarey <[hidden email]> wrote:
Hi Christophe, Can you get access to a Windows machine to try this... 1. Create a Standard User account with a password different from the default account... 2. Log in as the standard user account. 3. Without typing another password, install PharoLauncher from cheers -ben |
In reply to this post by Vitor Medina Cruz
Hi Vitor,
ok. That the point I missed. I think I will add a zip file with PharoLauncher for windows for user like you not having admin rights.
I need to think on the best way to handle that. Regards, Christophe. |
On Thu, Oct 12, 2017 at 3:43 PM, Christophe Demarey <[hidden email]> wrote:
Might this be a "portable" app, where downloaded images and VMs are stored next to the PharoLancher application, configured by a startup-setting file? Alternatively... searching around I found this... Also, when PharoLauncher is installed by an administrator and later used by a standard user, I guess there may be problems with Pharo needing to write changes to a restricted location?? Maybe that can be dealt with by... when a new user runs PharoLauncher from the start menu, copy it to their user folder $LocalAppdata\Programs\PharoLauncher and run PharoLauncher from there where they have privilege to write? btw, where are the NSIS source files accessible? Can they be dropped in the PharoLauncher git repo? HTH cheers -ben |
Hi Ben,
Good catch. probably by using RequestExecutionLevel = highest should solve the problem.
Yes, you could have problems but I do not think that adding more complexity to the installer is the way to go. I would rather prefer, in preference order: 1/ Pharo Launcher do not need to write data, 2/ if files need to be written, they should go to a Pharo data folder (e.g. $LocalAppdata\Programs\PharoLauncher) or to the user apps setting folder. What I would like is that a Pharo image writes data where it should
No because they are shared and used with other Pharo build scripts. Thanks for the information. Cheers, Christophe
|
Free forum by Nabble | Edit this page |