Activity

1. GeorgeBroughton commented on Jul 4, 2024

   

   George Daniel Broughton (GeorgeBroughton)

   on Jul 4, 2024

   Last edited by GeorgeBroughton

   More actions

   What you are suggesting would ultimately mean that every package maintainer who makes modules for powershell would have to provide bespoke instructions for alpine linux. It would be much more efficient if the maintainer for powershell under alpine would just provide those instructions, or implement install-module themselves.

   It seems this is also mentioned in Powershell's GitHub issues, so it's probably best to keep track of the issue there.

   Though, to answer where you could install the modules, you could put them in ~/.local/share/powershell/Modules according to some sources online.

   Let me know how that goes for you anyways. I'll spin up an alpine VM in a few and have a look into the problem.
2. leonyu commented on Jul 4, 2024

   

   Leon Yu (leonyu)

   on Jul 4, 2024

   Author

   More actions

   Instructions for installing Package Managers for a program language runtime is extremely common:

   • PIP offers instructions to install on Python install without PIP
   • Composer offers instruction to install on PHP
   • NPM used to offer ways to install itself on Node.js before it was fully bundled with Node.js.

   Package Manager should figure figure out which path it takes:

   • If it expects itself to be bundled with the language runtime, it should be available in all major distribution channels language runtime is available.
   • If it expects itself to not be bundled with the language runtime, it should have curl-esque instructions on how to install itself on a bare language runtime.
3. GeorgeBroughton commented on Jul 5, 2024

   

   George Daniel Broughton (GeorgeBroughton)

   on Jul 5, 2024

   More actions

   The instructions are in readme.md already.
   Your issue is due to a bug with the version of powershell distributed on alpine, which is documented in the link in my previous comment.

   The manual instructions are:

   Get PowerShellGet Source

   Steps

   • Obtain the source
   • Download the latest source code from the release page (https://github.com/PowerShell/PowerShellGet/releases) OR Clone the repository (needs git)

   git clone https://github.com/PowerShell/PowerShellGet
   

   • Navigate to the source directory

   cd path/to/PowerShellGet
   

   • Import the module

   Import-Module src/PowerShellGet -Force
   

   If import-module is also missing on your distro, this needs to be brought up with the maintainer of powershell for your distro, not here.
   Those commands are supposed to be usable by default, as stated in the issue I linked earlier.
4. leonyu commented on Jul 5, 2024

   

   Leon Yu (leonyu)

   on Jul 5, 2024

   Last edited by leonyu

   Author

   More actions

   The problem is due to lack of Import-Module.

   If import-module is also missing on your distro, this needs to be brought up with the maintainer of powershell for your distro, not here.

   Love your open source passion. However, I am going to draw the line here -- I am simply a user here to report a compatibility issue between 2 major pieces of open source software. It is not user's job to facilitate communications between software projects (e.g. distributor should bundle this, distributor could avoid that, distributor should run this test suite).

   In similar vein, if Photoshop has compatibility issues with Windows, do you expect a hobbyist designer to travel between Redmond and San Jose facilitate communication between Microsoft and Adobe?