PowerShell / PowerShell/PSResourceGet
PSGet needs to support selectively installing modules that support multiple platform runtimes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
As more module authors are trying to support cross-platform and cross-PowerShell (Windows PowerShell versions and PSCore6), PSGet should adopt same packaging as nupkg for multiple runtimes. Conceptually, the module author would layout their module like:
- MyModule
- Runtimes
- osx-x64
- win-x64
- win-x86
- linux-x64
- linux-arm32
- Runtimes
When user does install-module, it should only install the bits for the runtime that matches the system. save-module should probably save all the runtimes. Similar structure for differentiating PowerShell versions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing how install-module and save-module currently handle module package contents, then compare the proposed Runtimes layout with the linked NuGet multiple-target-framework guidance. Done means install-module selects the matching OS and architecture runtime while save-module preserves all runtimes, with a consistent approach for PowerShell versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100