Host PowerShell modules and scripts in NuGet Gallery? #24302
Replies: 2 comments 4 replies
-
|
Although PowerShell modules and dotnet libraries are packaged using the nuget format ( basically a zip file with metadata ) it does not mean they should be hosted together. The layout of a PowerShell module is completely different to that of a dotnet library or framework. They are not meaningfully interchangeable. They serve very different audiences, NuGet packages for dotnet developers and PowerShell Gallery for PowerShell developers and end users. I see no issue with PowerShell Gallery supporting both NuGet Protocol 3 and NuGet Protocol 2 simultaneously. I don't think hosting PowerShell modules at nuget.org would benefit either communities. |
Beta Was this translation helpful? Give feedback.
-
|
I'd much rather like PSG to support NuGet v3 and have known issues fixed. But where are the available resources (people, money, will, priority) to do it? There is no public info on roadmap, priorities, ETAs. They're however looking at adding ACR (Azure Container Registry) support to PSResourceGet, and it has been mentioned that Microsoft is considering to move their official modules to ACR, while keeping PSG a place for community modules and scripts. ACR is even less suited for PowerShell modules and scripts than NuGet Gallery, AFAIK. Given the above, I think using NuGet Gallery for PowerShell too would be the least bad option. |
Beta Was this translation helpful? Give feedback.
-
|
What are the known issues that make the existing PSGallery unusable? As far as I can tell it works. I don't care if it uses NuGet v2, NuGet v3 or the packages were hosted in a yum or apt repository or plain Azure blobs. What is important is that...
So far nothing is broken from that list. The only issue I have had with PowerShell packages is hosting them in github NuGet repository but I solved that for myself with rhubarb-geek-nz.NuGetPackage. But being able to use GitHub and lose PSGallery as the central repository would be a loss. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not saying PSG is unusable. If all you care about is getting the latest version of a script or module installed, it works just fine. If you want to do more advanced things with the API however. There are multiple issues with filtering on versions. I'd say thats core functionality to a package registry, being able to do various things with versions. Performance:
Uptime. If it's the central place for PowerShell users to get modules and scripts, one should be able to rely on it being up. With this discussion I'm thinking about the future. How will this be in 2 years, 5 years. Right now there are no major issues with PSG, as you say. But by the rate issues are addressed currently, that won't last forever. What would be the best plan moving forward to ensure we have one central place for hosting scripts and modules? Microsoft seems to think Azure Container Registry. |
Beta Was this translation helpful? Give feedback.
-
|
Lets look at it this way....
It really does not matter what the backend storage for those artefacts is as long as the cmdlets and UX still function, including Windows PowerShell Desktop 5.1. I do see problems with migrating packages without the publisher's consent. The model for both nuget.org and PSGallery is that publishers are in control of the packages they publish. I would not recommend automatically migrating packages without the publisher's knowledge or consent and them effectively loosing control over the visibility of (effectively) their property, or worse, a squatter taking their name and publishing a different package. In terms of "build it and they will come", if people find that hosting their packages at nuget.org is an advantage then let them do so. I have found it is not much help doing so at github.com. |
Beta Was this translation helpful? Give feedback.
-
|
I agree. It should not be a forced migration, but a new place people can opt into start using. |
Beta Was this translation helpful? Give feedback.
-
PowerShell Gallery and its API have various shortcomings and issues, which there does not seem to be resources available for looking into.
PowerShell Gallery is NuGet v2 based, with modifications. NuGet v2 itself is deprecated.
Would it be time better spent to look at hosting PowerShell modules and scripts in NuGet Gallery instead? With all the benefits it would bring, like NuGet v3, better API, piggyback uptime and features already in NuGet Gallery.
For a list of related issues I've collected and added to NuGet Gallery as a question for if they thought they could host PowerShell modules and scripts, see:
With a great reply reply with info on some of the changes that must be looked into for this to happen:
Beta Was this translation helpful? Give feedback.
All reactions