You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OneGet is not necessarily what we need. To install PowerShell modules, all we need is PSGet, which unfortunately depends on the module PackageManagement, which makes native calls.
And just to clarify, PowerShellGet, the module to obtain scripts from the PowerShell gallery, is called PSGet in the sources. This module is dependent on the PackageManagement library (aka OneGet) which is Windows-only and out of our scope.
We can get PSGet on Windows Core PowerShell if we get PSGet and its dependency ported to PowerShell repo(that is, build with .NET CLI so we can a) build the CoreCLR version and b) deploy it).
Spoke with Raghu Shantha (@raghushantha): we have the sources for OneGet etc. in the SD sync repo here. Adding some projects to build the necessary libraries for Windows should be pretty straight-forward.
Quoc Truong (@quoctruong) Can we sync to the latest sources from rs1 sd branch? I want to see if PackageManagement builds/works against the latest CoreCLR
Joey Aiello (@joeyaiello) which module is it pointing to? Keep in mind that on Windows, it inherits the environment's module path, so it'll show everything on the system (including in-box).
Also, it doesn't import on Windows (looks like a GAC problem?):
PS C:\Program Files\OpenPowerShell\0.5.0> ipmo psget Import-Module : Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
At line:1 char:1
+ ipmo psget
+ ~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Import-Module], FileNotFoundException
+ FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.PowerShell.Commands.ImportModuleCommand
Activity
andyleejordan commentedon Jan 30, 2016
OneGet is not necessarily what we need.To install PowerShell modules, all we need is PSGet, which unfortunately depends on the module PackageManagement, which makes native calls.andyleejordan commentedon Mar 9, 2016
And PackageManagement is OneGet. It was renamed.
This is blocked until OneGet is ported to Linux.
[-]Enable OneGet Module[/-][+]Enable PowerShellGet Module[/+]andyleejordan commentedon Mar 9, 2016
And just to clarify, PowerShellGet, the module to obtain scripts from the PowerShell gallery, is called PSGet in the sources. This module is dependent on the PackageManagement library (aka OneGet) which is Windows-only and out of our scope.
andyleejordan commentedon Apr 12, 2016
We can get PSGet on Windows Core PowerShell if we get PSGet and its dependency ported to PowerShell repo(that is, build with .NET CLI so we can a) build the CoreCLR version and b) deploy it).
andyleejordan commentedon Apr 12, 2016
Spoke with Raghu Shantha (@raghushantha): we have the sources for OneGet etc. in the SD sync repo here. Adding some projects to build the necessary libraries for Windows should be pretty straight-forward.
raghushantha commentedon Apr 12, 2016
Quoc Truong (@quoctruong) Can we sync to the latest sources from rs1 sd branch? I want to see if PackageManagement builds/works against the latest CoreCLR
andyleejordan commentedon Apr 12, 2016
sergei (@vors) Let's get latest SD changes to the psl-monad repo.
12 remaining items
andyleejordan commentedon Jun 20, 2016
Raghu Shantha (@raghushantha) Quoc Truong (@quoctruong) I believe you just enabled this, right? If so, can we add tests then close?
joeyaiello commentedon Jun 21, 2016
Andy Jordan (@andschwa) Raghu Shantha (@raghushantha)
Just popped open 0.5.0 on my Win10 box, and it's listing the module as
PSGetinstead ofPowerShellGet. Can we get that corrected before we close this?andyleejordan commentedon Jun 21, 2016
Joey Aiello (@joeyaiello) which module is it pointing to? Keep in mind that on Windows, it inherits the environment's module path, so it'll show everything on the system (including in-box).
joeyaiello commentedon Jun 21, 2016
The PowerShell Core one:
Also, it doesn't import on Windows (looks like a GAC problem?):
mgreenegit commentedon Jun 21, 2016
Also does not import on Ubuntu 14.04 LTS. Error is missing PackageManagement module.
raghushantha commentedon Jul 7, 2016
#1237, #1251 takes care of this