PowerShell / PowerShell/PSResourceGet
Support for platform-specific binary dependencies?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
I also have the same issue as e.g. on Windows need to generate my binary module using dotnet publish -r win10-x64 rather than dotnet publish to make it work locally (I believe the issue is to do with the SQLite driver for EF Core).
This makes it a bit tricky to publish a cross-platform binary module via PowerShell Gallery....
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 reproducing the Windows case with dotnet publish -r win10-x64 versus dotnet publish, focusing on the SQLite driver for EF Core. Trace how PSResourceGet packages and publishes binary PowerShell modules, then define what runtime-specific dependency support must do for a cross-platform PowerShell Gallery package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell, sqlite
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100