Using MyGet as a OneGet package source
blog.myget.org
Using MyGet as a OneGet package source
1–7 of 7 posts
Re: Using MyGet as a OneGet package source
#2Great service those guys provide.
If you're doing .NET development you should give it a try.
Re: Using MyGet as a OneGet package source
#3How does oneget relate to ripple?
Re: Using MyGet as a OneGet package source
#4How does oneget relate to ripple?
Ripple is more aimed at dependency management of components. Much like NuGet (in fact it uses NuGet) combined with direct fetching from Git repos, better resolving of dependencies and such.
OneGet is more aimed at installing system components. It is like Chocolatey (and in fact uses Chocolatey under the hood).
Re: Using MyGet as a OneGet package source
#5How does oneget relate to ripple?
Ripple is more aimed at dependency management of components. Much like NuGet (in fact it uses NuGet) combined with direct fetching from Git repos, better resolving of dependencies and such. OneGet is more aimed at installing system components. It is like Chocolatey (and in fact uses Chocolatey under the hood).
Thanks, looks like I totally misunderstood oneget. It is more intended to pave a clean machine with the correct products and libraries?
Re: Using MyGet as a OneGet package source
#6How does oneget relate to ripple?
Ripple can be considered as another solution-level package manager, much like NuGet. That's as far as I can tell there's any relationship :)
Re: Using MyGet as a OneGet package source
#7Are there any plans to add support for other OPC sources to OneGet? I can imagine a Windows8StoreProvider would be very useful, especially if you can provide those through MyGet too.