Justin Grote

Looks to me like you're using `install-module`, so that would be for the v2 version of this module, the issues have been moved here: https://github.com/PowerShell/PowerShellGetv2 That said, a guess would...

My workaround for this was to, before loading any modules, update package management "manually" by pulling it from the PSGallery URI and unzipping it in-place before importing it, this way...

Related Linux should follow DBG conventions and save it in ~/.config/powershell/Modules

Install Path locations are pseudo-hard coded into PSGetV2 and PSGetV3. Either those modules should expose an API for the install locations or (even better), PowerShell engine should have an API...

Here is where it is defined in PSGetv3 https://github.com/PowerShell/PowerShellGet/blob/2b4dab36195453edbd85789c9fdb8353b7c6130e/src/code/Utils.cs#L680-L707 And PSGetV2 https://github.com/PowerShell/PowerShellGetv2/blob/5aba7531f526b6e60b2757c36799995597b6dcec/Tests/PSGetTestUtils.psm1

Tools like Scoop and their manifest are a great example of how to do this right with Git repositories. I think right now the main focus should be parity with...

@Ayanmullick the source code is right there, you could attempt a PR, though they aren't taking PRs at the moment :)

This is actually covered in the RFC as the -DestinationPath parameter. I suggest it be altered to `-Destination` because this would be more familiar to most Powershell users since Move-Item,...

I would suggest it on Save since most users are familiar with that workflow from 2.x for putting modules in a location other than the default modules directories., and the...

One issue here is you're going to need to check all existing modules for their requiredmodules and preserve any pinned versions as well, otherwise you're going to break those modules...