-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can we integrate this with Chocolatey? :) #2
Comments
Holy shit, it's Rob from Chocolatey!! Look what you've started, now everyone's trying to create their own Windows package manager ;) Thanks for checking out my attempt. I know you're only kidding about Chocolatey integration, but I'd be keen to collaborate—it seems like we're on similar missions. |
Not really kidding. You can make nuget pkgs a known format and take I'm thinking of something similar in choco for scoop, much like we do with On Thursday, October 3, 2013, Luke Sampson wrote:
Rob http://devlicio.us/blogs/rob_reynolds |
Oh right—but then why wouldn't you just have Chocolatey and Scoop installed so you can use both? I do. |
True story. On Thursday, October 3, 2013, Luke Sampson wrote:
Rob http://devlicio.us/blogs/rob_reynolds |
Am hoping for more clients at some point. Choco doesn't need to be the only On Thursday, October 3, 2013, Rob Reynolds wrote:
Rob http://devlicio.us/blogs/rob_reynolds |
Chocolatey is always going to the best client for Chocolatey infrastructure ;) Although—has anyone come up with a GUI client for Chocolatey yet? That would be a great alternative to the Windows 8 App Store. Meanwhile, Scoop's designed to work with a bare minimum of infrastructure—a git repo pointing to some zip files somewhere on the web. I think this is a strength for Scoop, because it doesn't attempt to do everything that Chocolatey can do. And fortunately for everyone on Windows, Chocolatey is there to handle the full-spectrum of install scenarios. |
There's also CoApp which has some differing goals but plays in the same space. |
I just found this...this is super neat...
The text was updated successfully, but these errors were encountered: