-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Support for Chocolatey/NuGet v2 in packages #21294
Comments
I did not test it but can't you just use the NuGet registry as a Chocolatey registry? |
Unfortunately you cannot. While you can apparently still So for Chocolatey, we would need the v2 version of the NuGet API, which I understand is quite old and deprecated on the NuGet side of things. Hence it would make sense to leave NuGet alone and consider it as a Chocolatey API, especially if it were ever to include any of their “enhancements”. Though I don't think those are strictly necessary, if someone were to figure them out, they don't belong with vanilla NuGet. |
Ah, missed that they only support v2, thanks. I will have a look at the v2 api spec. |
I have added #21393. Could you test this PR? |
So far so good! It works for everything I use it for. I can push, list, info, and install without complaint. |
Fixes #21294 This PR adds support for NuGet v2 API. Co-authored-by: Lauris BH <lauris@nix.lv> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Feature Description
I'd like to suggest an addition to the Packages feature...Chocolatey packages. As an API reference, this would require NuGet v2 support(I understand there are some enhancements for a full-featured Chocolatey repo but NuGet v2 is the base). Additionally, this would change up the package view page with references to chocolatey commands, e.g.
choco push
andchoco install
instead of thedotnet
NuGet commands. I personally would try to put choco:// links on the page but that protocol is unofficial.While Chocolatey will eventually upgrade to support NuGet V3, and technically you could use Gitea's NuGet API as a repo at that point, there is no set date on that upgrade and the pages would reference
dotnet
commands.Thoughts?
Screenshots
No response
The text was updated successfully, but these errors were encountered: