glab installation through winget does not add glab as recognized executable
Description
When I installed glab using the winget instructions provided in the readme, I couldn't run glab from the command line because it is not recognized.
Expected Behavior vs Actual Behavior
I expect that the command line app is available immediately after install, but this is not the case.
Steps to Reproduce
I installed using the following:
winget install --exact glab
By the way, please note that the command provided in the docs, namely winget install glab does not work as there exists another in msstore which starts with those same letters.
The installation ran successfully. The logs are as follows (in Dutch):
Gevonden glab [GLab.GLab] Versie 1.21.1
Deze applicatie is aan u in licentie gegeven door de eigenaar.
Microsoft is niet verantwoordelijk voor en verleent geen licenties aan pakketten van derden.
Downloading https://github.com/profclems/glab/releases/download/v1.21.1/glab_1.21.1_Windows_x86_64_installer.exe
De installatie-hash is geverifieerd
De installatie van het pakket wordt gestart...
I then tried a simple glab from the command line, which threw the following error:
glab : The term 'glab' is not recognized as the name of a cmdlet,
function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
+ glab | clip
+ ~~~~
+ CategoryInfo : ObjectNotFound: (glab:String) [], CommandNot
FoundException
+ FullyQualifiedErrorId : CommandNotFoundException
I tried a refreshenv, then glab. I also tried running from a new terminal but none of these things worked.
Your Environment
Windows 10, with glab version 1.21.1 I assume
+1
Hi @brodock, thanks for reporting this issue.
Is this issue still valid for v1.22.0 ?
Can confirm the same behaviour with 1.22.0 installed via WInGet. The PATH entry is added for all users I seem to have solved this by adding a \ to the end of the path.
This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues.
It wasn't me who have reported it :) @awa5114 would you mind double checking if this is still a problem?
This issue has been automatically marked as stale because it has not had recent activity. We haven't had the time to address it yet, but we want to keep it open. This message is just a reminder for us to help triage issues.