Your Guide to the Latest Windows Server Product Information
· Manage a list of software repositories in which packages can be searched, acquired, and installed
· Search and filter your repositories to find the packages you need
· Seamlessly install and uninstall packages from one or more repositories with a single PowerShell command
I really don't like the oneget functionality being stapled to WMF 5. I am not at all opposed to FOSS, but it shouldn't be in WMF 5. It should be a module people optionally choose to install, manually - I recognize that someone who has admin rights can install whatever they want to a machine, and could already use PS to pull from chocolatey if they chose to, but the reality of the functionality is that it's adding a direct line to something I inherently DO NOT TRUST in my environment.I think what bothers me about it is that it asserts a false sense of trust - "the oneget module is core to Powershell, the things I can download must be vetted and safe". Few people feel nervous pulling software from microsoft.com for that reason... Chocolatey isn't Microsoft.com, though, and just because someone may choose to implicitly trust Microsoft doesn't mean that I trust chocolatey - it's a vector into my machines that I don't trust in the slightest, I applaud open source options and use them a lot myself, but I feel it's a mistake and a security risk to make it a mandatory part of the management framework.
@Daniel - You are correct to be concerned about security of downloading and installing community bits. The reality is that you don't know who is vouching for the bits in the community repository and thus whether they can be trusted or not. That is why when you do a Get-PackageSource, you'll see that we let you declare whether a source is TRUSTED or not. By default, the community repository is not trusted and therefore we will ask you about this when you download software from it.So yes - it is a concern and you'll see us doing a lot of work in this space but I have nothing to announce today. Cheers!Jeffrey Snover [MSFT[
I'm glad to see the package management situation being addressed. I am concerned that OneGet is following the Chocolaty path of installing these packages outside "Program Files*" to thwart UAC. If so, it's a non-starter for the company I work at and me personally.
Thank you for your considerations Jeffrey Snover, i'm really exited about this new upcomming version, i hope to see a whole load of new functionalities :)
I'm hoping that DSC for switching/routing is on the way. The power of that would be phenomenal.....
And once again, Microsoft makes its Operating Systems more like its Linux counterpart. Don't get me wrong, there is nothing wrong with wanting to be like Linux.... but after years of insisting CLI is dead, look where we are. On a side note, this is all in the interest of deprecating WMI into a CLI rather than an API, which I think might be a step backwards, but I guess it is more accessible despite going against the current trend of 'program more'
Well done, Microsoft! Your very own package manager! Welcome to the 1990's!
Good to see package management coming to WMF. Can't wait to start playing with it!
Why are you not using a fixed width font in the console? The screenshots will be way nicer...
I tried out OneGet module today and its nice(read my review at http://techibee.com/powershell/what-is-chocolatey-in-powershell-v5/2241). I am just wondering how many firms will try to make use of it given it is installation from third party web services. If building similar repositories in house is easy, then its a great tool. However, I like the idea very much and looking forward for its evolution in coming releases.
stay tuned for updates on new oneget puppet provider I'm writing here-
Today you can use my chocolatey provider with chocolatey. It rocks.
The preview is currently only 2012R2 & 8.1 -- will the GA version include previous Windows versions?
Creating private repositories is very simple. One way is to create an empty ASP.NET Web Application in VS and add the nuget.server from the library package manager. Deploy to an IIS host and you're pretty much up and running. We just deployed a nuget server farm and are putting it into production next week. Very easy, very slick.