Chocolatey Provider and Choco.exe incompatibilities

[CMCDragonkai]

Refer to:

• installing chocolatey via OneGet nukes C:\Chocolatey\bin OneGet/ChocolateyProvider#4
• Provider creates Chocolatey install dir at root of C: OneGet/ChocolateyProvider#3

Will this be fixed?

I wanted to use OneGet's chocolatey provider to install things and then try using the choco.exe to create a new package, but my C:\Chocolatey\bin directory got destroyed.

[ferventcoder]

It will be fixed when we have a supported OneGet Provider.

[ferventcoder]

Right now perhaps use Chocolatey-Get instead?

[masaeedu]

@ferventcoder Might be a good idea to link to that in the README, can be removed when this is ready.

[ferventcoder]

@masaeedu good idea!

[ferventcoder]

Done! 2b4538f

[heaths]

What would it take to get a support provider? Since PackageManagement (formerly OneGet) is installed by default on Windows Server Core, we'd like to enable easy acquisition of packages on a windowsservercore docker container image. Isn't this now the official OneGet provider according to the OneGet project page, are there any particular issues that need resolving to release an update that unifies where tool program stubs are located?

[ferventcoder]

Howdy - please see #5