These are chat archives for chocolatey/chocolatey-oneget

27th
Jul 2016
Derek Schauland
@webjunkie_twitter
Jul 27 2016 15:25
I'm trying to figure out how to get a constant installation of a chocolatey package using the PowerShell method install-package ... Is it possible to get these to live in c:\program files\ rather than a seemingly random temp folder? thx
dragon788
@dragon788
Jul 27 2016 15:57
you can pass a specific folder to install a package to per package
the actual installs happen to C:\ProgramData for the most part because this requires Administrator permissions and prevents any tampering with the programs
Derek Schauland
@webjunkie_twitter
Jul 27 2016 16:02
When I run the script with -verbose it lists the installing directory as c:\users\user\appdata\local\temp\randomnumber but the randomnumber dir doesn't exist in \temp when I go chasing it
Also running get-package sysinternals indicates it is not installed
dragon788
@dragon788
Jul 27 2016 16:26
I believe that the choco provider is currently in beta, it has been recommended to just use regular Chocolatey while they sort out some of the issues with OneGet/PowerShellGet
does install-package report any errors when installing?
also, do you have PsGet or any other providers enabled?
Derek Schauland
@webjunkie_twitter
Jul 27 2016 16:32
The chocolatey package source is available but it doesn't appear under package providers... although I do not recall if it had before
no errors with install-package
Rob Reynolds
@ferventcoder
Jul 27 2016 16:33
@webjunkie_twitter definitely want to wait for the official provider if you want to use Chocolatey in any capacity. We have a newsletter you can subscribe to and await for the official OneGet provider
for now, we definitely suggest you stick with either choco.exe or ChocolateyGUI for the best support and fixes, including any security issues that have been handled since the preview for the OneGet provider was released
Derek Schauland
@webjunkie_twitter
Jul 27 2016 16:46
Cool Ill give that a shot
thanks