Skip to content

Commit 72ecfda

Browse files
committed
add clarity on applicability to only system32
1 parent a418431 commit 72ecfda

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

2-Draft-Accepted/RFCNNNN-PSCore6-and-Windows-Modules.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -56,8 +56,8 @@ Duplicate modules are something that can be addressed in PowerShellGet and outsi
5656

5757
Modules in `Program Files` that may be compatible with PowerShell Core 6 is addressed below.
5858

59-
Modules in the PowerShell Core `PSModulePath` are implicitly deemed compatible even if the manifest does not
60-
declare compatibility.
59+
Modules _not under_ Windows System32 path, for example in the PowerShell Core `PSModulePath`, are implicitly deemed compatible even
60+
if the manifest does not declare compatibility.
6161
A user who explicitly uses `Install-Module` within PowerShell Core 6 expect those modules to be available to PowerShell Core 6.
6262

6363
### CompatiblePSEditions for Windows System32
@@ -74,7 +74,7 @@ Similarly, module auto-discovery and auto-loading will only find modules that ar
7474

7575
The `ModuleInfo` table format will add a column for `PSEditions` (shortened from `CompatiblePSEditions` between `Name` and `ExportedCommands`).
7676

77-
### Using Modules not declared as Compatible
77+
### Using Modules from System32 not declared as Compatible
7878

7979
`Get-Module -ListAvailable` will support `-SkipCompatibilityCheck` switch to list all modules in `PSModulePath`.
8080

0 commit comments

Comments
 (0)