My installer detects if it was run as root/admin or normal user and then sets <addEnvironmentVariable> and <addEnvironmentVariable> to update the <scope> to system or user variables. On MS Windows, the installed updates registry values as I would expect, in the HKEY_CURRENT_USER\Environment\ for users and HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Environment\ for system updates.
On Linux, updates to <scope> with either system and user values change the $HOME/.bashrc and $HOME/.profile files. In effect, does this mean there is no difference between <scope> system/user values on Linux? To make a difference, would it be better to update the respective /etc/bash.bashrc and /etc/profile files when <scope> is system?
asked 05 Jul '12, 00:23
I have added your suggestion of modifying environment variables for Unix systems using
However, investigating and planning this feature may take some time to investigate as the files where this should be put may be different for various shells and/or distributions that would have to be supported.
Also, I apologize for the late response. Due to an issue with notification system, we have missed this question.
answered 23 Jul '12, 08:22
Is there any updates on this? The correct way is to put the environment variables the way that tahoar suggest atleast if they are system wide. Maybe it should be two valid options for this. addEnvironmentVariable and maybe an addSystemEnvironmentVariable or something like that?
answered 24 May '16, 07:43