-
Notifications
You must be signed in to change notification settings - Fork 520
use PSGet v3 #2932
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use PSGet v3 #2932
Conversation
:(
(削除) I added a Get-Module and gmo -list PSGet as a way to make sure the compat module works. Is this the best way? (削除ここまで)
Ah I see, it gives a warning, nice:
but also :( for the error. @JamesWTruher?
I like to run (get-command find-module).module.modulebase to make sure the module that's actually loaded is the right one.
@alerickson Good to know!
I guess in this context it might make more sense to run ((get-command find-module).module).Version
This is an odd error to me. Why is it spelled "Powershell" in the path?
Okay, just updating with convo Tyler and I had offline: beta9 is the latest psget release that handles some unix path changes, there is however, a bug with the -debug param in Install/Save (I realize it's not being used right now, just a warning)
.vsts-ci/templates/ci-general.yml
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't need -AllowClobber for PSGet since it's entirely new cmdlet names
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'll scale better once PSGet v3 ships with PowerShell.
ok I'm gonna stop here for now. Looks like we have some more work:
- PSGallery version problem (
beta10is being treated as the version betweenbeta1andbeta2instead of afterbeta9) - PSGet doesn't register PSGallery by default (forcing me to run
Register-PSResourceRepository -PSGallery) - Looks like either the compat module or the main module are prompting for something even though I specified
-Force
PSGet doesn't register PSGallery by default (forcing me to run Register-PSResourceRepository -PSGallery)
Surely that's a bug, right? I know, don't call you Shirley.
@rkeithhill personally I agree with you. I think PSGet v3 should register PSGallery by default. I only did it in the commit to see what would happen if it was already registered.
This moves us to use the latest preview of PowerShellGet v3 and the compat PSGet module