[Enhancement] use chocolatey path on system without reboot

[rismoney]

With an assist from this - http://poshcode.org/2049... if an option is specified... thoughts?

user path currently is good, and minimal priveledges, etc...

[ferventcoder]

WHAT?! That's awesome.

[rismoney]

http://poshcode.org/3537

Going to test this one- 7 week's old...

[mwrock]

I think rob and @Iristyle were looking at his yesterday and found that it did not work. I ran into this issue a couple weeks ago and also tried this without luck. Not sure if thats because powershell.exe does not subscribe to the broadcasts.

I did find however that this:

$paths=(Get-WmiObject Win32_Environment | where-object -filter {$_.Name -eq 'path'})
foreach($path in $paths) {$newPath += $path.VariableValue}
Write-Host $newPath

does work. It was mentioned though that "Path" may not be enough. There could be other variables that other programs might expect (like JAVA_HOME). Also, this needs to be batch file compliant as well. I believe @Iristyle was going to implement something that would work for both ps and dos. See the Issue #153 for the details of the discussion.

[rismoney]

yea, i went to the authors website- http://mnaoumov.wordpress.com/2012/07/24/powershell-add-directory-to-environment-path-variable/ and right at the top, is his note...:( fail

[mwrock]

This is still an open issue. The above pull request only fixes Chocolatey's ability to refresh its own view but does not refresh the view of the user session. Need to add some bath flavored means of refreshing a normal command line. Also need to provide a means of refreshing PS users most likely via their $Profile.

[ferventcoder]

The initial workings for this are in b87541a - we'll see what other things crop up.

[AnthonyMastrean]

I'm excited about this one, need it for some complicated packages that depend on the hg and 7zip command line packages first, to enable installing itself (hggit).

[ForNeVeR]

Hey, guys. What if I'm running chocolatey from the existing PowerShell session? It seems that PowerShell starts the new cmd process for the chocolatey.bat invocation, and your solution will instead refresh the environment only for the freshly started cmd and not the caller shell.

What can I do to refresh the caller PowerShell session environment? Maybe there should be an alternative C:\Chocolatey\bin\chocolatey.ps1 for such cases? What you think?

Ew, and then we have to reimplement the whole RefreshEnv.cmd with PowerShell. I still think it can be modified to construct the %TEMP%\_env.ps1 file with PowerShell syntax instead of %TEMP%\_env.bat with cmd syntax.

[ferventcoder]

@ForNeVeR We already have the powershell refresh in and once the commands become aliases back to the module methods, you will see this happen automatically as there will be no call out to a batch and then back into powershell.

[ForNeVeR]

Thank you for response, that's a good news.

[ferventcoder]

Fixed in a09e158

[ferventcoder]

The current state is that unless you import the chocolateyinstaller module, you won't automatically get path updates. Importing the module isn't recommended at this time but some folks are experimenting with it.

With cmd.exe you can just call RefreshEnv after an install that would update something in your environment and it will update your session's environment.