Skip to content

"Find-Command" & "Install-Module" cmdlets should identify OS compatibility #79

Open
Open
"Find-Command" & "Install-Module" cmdlets should identify OS compatibility#79
Labels
Area-ErrorHandling
Milestone
vNext

Description

@SteveL-MSFT
Steve Lee (SteveL-MSFT)
opened on Oct 17, 2016

From Maximo Trinidad (@MaximoTrinidad) on September 28, 2016 13:29

Steps to reproduce

In Linux, using either Find-Command or Install-Module, will list all available (Windows and Linux).

Expected behavior

Install the module that can be executed Linux, as well as Windows.

It maybe a good idea to have these cmdlets check for the OS type before providing the list.

Actual behavior

A Module won't install because it need dependencies, or was built for Windows OS. Below, example has been addressed;
janegilring/PSVersion#5

psversionissue

Environment data

Linux: Ubuntu 16.04.1 64bit

PS /home/maxt> $PSVersionTable                                                  

Name                           Value                                           
----                           -----                                           
PSVersion                      6.0.0-alpha                                     
PSEdition                      Core                                            
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}                         
BuildVersion                   3.0.0.0                                         
GitCommitId                    v6.0.0-alpha.10                                 
CLRVersion                                                                     
WSManStackVersion              3.0                                             
PSRemotingProtocolVersion      2.3                                             
SerializationVersion           1.1.0.1

Copied from original issue: PowerShell/PowerShell#2374

Activity

  1. SteveL-MSFT commented on Oct 17, 2016

    @SteveL-MSFT
    Steve Lee (SteveL-MSFT)
    on Oct 17, 2016
    MemberAuthor

    From Joey Aiello (@joeyaiello) on September 29, 2016 16:35

    We've talked about this in the past. My only reservation here is that many module authors won't know that they are actually compatible (or mostly compatible) with macOS or Linux, and I'd rather not prevent users from installing those modules. (E.g. posh-git is 99% working on Mac/Linux)

    Maybe we should offer a warning at install time if compatibility isn't explicitly listed?

    I also agree we should absolutely give users a way to explicitly filter by Edition.

  2. joeyaiello commented on Mar 17, 2017

    @joeyaiello
    Joey Aiello (joeyaiello)
    on Mar 17, 2017

    Manikyam Bavandla (@bmanikm) we have a customer who has an external dependency on this right now, we should talk offline about how we might be able to get this prioritized

  3. bmanikm commented on Mar 17, 2017

    @bmanikm
    Manikyam Bavandla (bmanikm)
    on Mar 17, 2017
    # Find modules supported on PowerShell Core edition
Find-Module -Tag PSEditon_Core

    For more details, please take a look at the below documentation on explicitly filtering the items by Edition.

  4. Joey Aiello (joeyaiello)
    changed the title [-]"Find-Command" & "Install-Module" cmdlets show identify OS compatibility[/-] [+]"Find-Command" & "Install-Module" cmdlets should identify OS compatibility[/+] on Mar 30, 2017
  5. alerickson
    transferred this issue fromPowerShell/PowerShellGetv2on Mar 30, 2020
  6. Sydney Smith (SydneyhSmith)
    added
    vNext
    Area-ErrorHandling
    on Mar 30, 2020
  7. Steve Lee (SteveL-MSFT)
    added this to the vNext milestone on Sep 4, 2020
  8. Steve Lee (SteveL-MSFT)
    removed
    vNext
    on Sep 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-ErrorHandling

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions