Skip to content

"Find-Command" & "Install-Module" cmdlets show identify OS compatibility #2374

Description

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  

Activity

  1. joeyaiello commented on Sep 29, 2016

    @joeyaiello
    Contributor

    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. SteveL-MSFT commented on Oct 17, 2016

    @SteveL-MSFT
    Member

    This issue was moved to PowerShell/PowerShellGet#19

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-PowerShellGetspecific to PowerShellGet moduleResolution-ExternalThe issue is caused by external component(s).

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions