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

[SteveL-MSFT]

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

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

[SteveL-MSFT]

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.

[joeyaiello]

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

[bmanikm]

# 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.

• Items with compatible PowerShell Editions
• Modules with PSEditions
• Scripts with PSEditions