Skip to content
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

PowerShell Modules from PowerShellGet #687

Open
Witchilich opened this issue May 25, 2020 · 2 comments
Open

PowerShell Modules from PowerShellGet #687

Witchilich opened this issue May 25, 2020 · 2 comments
Labels
Area-Settings Issue related to WinGet Settings Issue-Feature This is a feature request for the Windows Package Manager client. PowerShell Issue related to WinGet PowerShell Module or cmdlet

Comments

@Witchilich
Copy link

Description of the new feature/enhancement

Windows Store apps seems to be in the roadmap, but PowerShell Modules from PowerShellGet should be too.

Proposed technical implementation details (optional)

For winget to be the one package manager for all our packages it also needs to include PowerShell modules.

@denelon denelon transferred this issue from microsoft/winget-pkgs Jan 6, 2021
@ghost ghost added the Needs-Triage Issue need to be triaged label Jan 6, 2021
@denelon denelon added Issue-Feature This is a feature request for the Windows Package Manager client. and removed Needs-Triage Issue need to be triaged labels Jan 6, 2021
@o-l-a-v
Copy link

o-l-a-v commented Nov 12, 2021

This would be awesome. There's no neat way to keep PowerShell modules updated, which also fixes removing old versions of modules. I've scripted my way around it, but it's sloooow and its not slow anymore. Other alternatives:

Maybe WinGet could add NuGet v2 ( powershellgallery.com ) and v3 ( nuget.org ) support with the ability to:

  1. Install and update PowerShell modules and scripts
  2. Handle scopes: user context (not require admin) and system context
  3. Optionally install to non-default path, because
  4. Handle update to PSModulePath environment variable

Why stop at PowerShell modules and scripts? NuGet Gallery / https://www.nuget.org/ would be cool too.

@denelon
Copy link
Contributor

denelon commented Feb 18, 2022

When we start the deeper work on:

We should consider a mechanism to detect if a newer version of the PowerShell module is available to make it easier to upgrade, and possibly a setting to automatically pull the latest module down when that case is true.

@denelon denelon added the Area-Settings Issue related to WinGet Settings label Feb 18, 2022
@denelon denelon added the PowerShell Issue related to WinGet PowerShell Module or cmdlet label Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Settings Issue related to WinGet Settings Issue-Feature This is a feature request for the Windows Package Manager client. PowerShell Issue related to WinGet PowerShell Module or cmdlet
Projects
None yet
Development

No branches or pull requests

3 participants