OneGet - anyone using it?
-
OK after reading through a blog post by one of the creators of OneGet, I think I get it.
OneGet is a package manager, manager. Currently there are two package managers that OneGet knows about
nuget
chocolateyWhat this means - people can create packages in either nuget or chocolatey (which uses nuget) to create software packages and publish them into a software repository. Then that person or others can connect to the repository and install that software from those packages.
So my question is - is it worth learning the OneGet specific commands vs skipping them and only using the chocolatey commands since there are currently so few package managers that work with OneGet - and who knows if there ever will be.
And odd thing, over in the git readme they list that there is a PowerShellGet package manager, but when you run Find-PackageProvider it's not listed.
-
Well, from what I can tell, Chocolatey is already a package manager for NuGet. So OneGet is mostly just replacing Chocolatey more than anything else, but not quite as you pointed out, as it requires it. It's more like it just extends Chocolatey.
-
I see the point that OneGet is trying to make - if there were 10 different repos all providing their own type of packages - OneGet could stand in front of them all and install/uninstall software.
But a year and a half in and we still only have two (nuget and Chocolatey) and it appears that the PowerShellGet one might have failed, soooo - are package repos dieing as an idea for MS?
-
@Dashrender said in OneGet - anyone using it?:
I see the point that OneGet is trying to make - if there were 10 different repos all providing their own type of packages - OneGet could stand in front of them all and install/uninstall software.
Isn't that the description of Chocolatey?
-
uhhh I don't know - I guess... Can nuget manage packages or only make them? Can Chocolatey only manage them and not make them?
-
@Dashrender said in OneGet - anyone using it?:
uhhh I don't know - I guess... Can nuget manage packages or only make them? Can Chocolatey only manage them and not make them?
Well Chocolatey just automates NuGet. What functionality is OneGet adding is the big question.
-
@scottalanmiller said in OneGet - anyone using it?:
@Dashrender said in OneGet - anyone using it?:
uhhh I don't know - I guess... Can nuget manage packages or only make them? Can Chocolatey only manage them and not make them?
Well Chocolatey just automates NuGet. What functionality is OneGet adding is the big question.
OneGet is automating Chocolatey and any other package managers you install. From the above linked post - the idea is that you can use anything you want for a package creator/manager.. and then manage them all through OneGet.
I have a better question - why isn't MS doing this through through the MS store instead? Even on Server?
-
@Dashrender said in OneGet - anyone using it?:
@scottalanmiller said in OneGet - anyone using it?:
@Dashrender said in OneGet - anyone using it?:
uhhh I don't know - I guess... Can nuget manage packages or only make them? Can Chocolatey only manage them and not make them?
Well Chocolatey just automates NuGet. What functionality is OneGet adding is the big question.
OneGet is automating Chocolatey and any other package managers you install. From the above linked post - the idea is that you can use anything you want for a package creator/manager.. and then manage them all through OneGet.
I have a better question - why isn't MS doing this through through the MS store instead? Even on Server?
meaning... why isn' tthe Store sciptable? I think the answer is because the Store is a totally useless piece of crap and this is how actual Windows package management has to be.
