Skip to content

Enable PowerShellGet Module #463

Closed
Closed

Description

See OneGet. It would great to enable this module with its PowerShell provider so that PowerShell modules can be installed automatically.

Activity

  1. andyleejordan commented on Jan 30, 2016

    @andyleejordan
    MemberAuthor

    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.

  2. andyleejordan commented on Mar 9, 2016

    @andyleejordan
    MemberAuthor

    And PackageManagement is OneGet. It was renamed.

    This is blocked until OneGet is ported to Linux.

  3. changed the title [-]Enable OneGet Module[/-] [+]Enable PowerShellGet Module[/+] on Mar 9, 2016
  4. andyleejordan commented on Mar 9, 2016

    @andyleejordan
    MemberAuthor

    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.

  5. andyleejordan commented on Apr 12, 2016

    @andyleejordan
    MemberAuthor

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

  6. andyleejordan commented on Apr 12, 2016

    @andyleejordan
    MemberAuthor

    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.

  7. raghushantha commented on Apr 12, 2016

    @raghushantha
    Member

    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

  8. andyleejordan commented on Apr 12, 2016

    @andyleejordan
    MemberAuthor

    sergei (@vors) Let's get latest SD changes to the psl-monad repo.

  9. 12 remaining items

  10. andyleejordan commented on Jun 20, 2016

    @andyleejordan
    MemberAuthor

    Raghu Shantha (@raghushantha) Quoc Truong (@quoctruong) I believe you just enabled this, right? If so, can we add tests then close?

  11. joeyaiello commented on Jun 21, 2016

    @joeyaiello
    Contributor

    Andy Jordan (@andschwa) Raghu Shantha (@raghushantha)

    Just popped open 0.5.0 on my Win10 box, and it's listing the module as PSGet instead of PowerShellGet. Can we get that corrected before we close this?

  12. andyleejordan commented on Jun 21, 2016

    @andyleejordan
    MemberAuthor

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

  13. joeyaiello commented on Jun 21, 2016

    @joeyaiello
    Contributor

    The PowerShell Core one:

    PS C:\Program Files\OpenPowerShell\0.5.0> get-module -li PSGet                                                          
    
        Directory: C:\program files\openpowershell\0.5.0\Modules
    
    
    ModuleType Version    Name                                ExportedCommands
    ---------- -------    ----                                ----------------
    Script     1.0.0.1    PSGet                               {Install-Module, Find-Module, Save-Module, Update-Module...}
    

    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
    
  14. mgreenegit commented on Jun 21, 2016

    @mgreenegit
    Member

    Also does not import on Ubuntu 14.04 LTS. Error is missing PackageManagement module.

  15. raghushantha commented on Jul 7, 2016

    @raghushantha
    Member

    #1237, #1251 takes care of this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Area-PackageManagementspecific to PackageManagement module (aka OneGet)Area-PowerShellGetspecific to PowerShellGet module

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions