Skip to content
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

Commands should be available to the console after install #222

Open
tbalasavage opened this issue May 19, 2020 · 14 comments
Open

Commands should be available to the console after install #222

tbalasavage opened this issue May 19, 2020 · 14 comments
Labels
Area-Path Issue related to path environment variable Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@tbalasavage
Copy link

Brief description of your issue

I've installed the GitHub CLI and then attempt to run it but it fails each time.
image

Steps to reproduce

winget install github.cli
gh

Expected behavior

gh brings up GitHub CLI info.

Actual behavior

An error is produced

Environment

image

Any other software? No

@utybo
Copy link

utybo commented May 19, 2020

For some reason, it looks like gh isn't available directly in the PATH. It worked for me when I opened a new powershell window.

@dhrrgn
Copy link

dhrrgn commented May 20, 2020

This is likely do to the session needing reloaded. Basically, it added it, but your current PS session doesn't know about it yet. This is normal (same thing happens in all *nix shells).

That being said, it would be nice if winget automatically refreshed the path. Maybe a flag could be added to the manifest file to trigger this.

Another option would be to provided a command like winget session refresh. This is what Chocolatey does (Update-SessionEnvironment or refreshenv)

@tbalasavage
Copy link
Author

@dhrrgn I think that you're correct because when I opened a new PS Core shell today, it worked as expected. I was confused yesterday because I opened a new tab in Windows Terminal after installation and received the same error message. When I opened a new and independent PS Core shell, it worked as expected today.

Regarding what you said about *nix above, if I use dnf or apt to install an application, the application is available for immediate use and doesn't require a new window. Are they doing something akin to what you suggest above?

@JohnMcPMS JohnMcPMS changed the title GitHub CLI installs but isn't available on path Commands should be available to the console after install May 20, 2020
@JohnMcPMS
Copy link
Member

@dhrrgn is correct, we don't currently reload the session. I'm going to change the title to indicate the feature request.

@JohnMcPMS JohnMcPMS added the Issue-Feature This is a feature request for the Windows Package Manager client. label May 20, 2020
@dmoncada
Copy link

dmoncada commented May 21, 2020

I ran into a similar problem when trying to install python: winget install python

After the Python installation wizard launched and finished, the tool reported: Successfully installed. But python was not automatically added to my path (reloading the session didn't help here, running $ python in the terminal takes me to the "Get Python" page in the Microsoft Store), though the python.exe was installed to the following location:

C:\Users\<username>\AppData\Local\Programs\Python\Python38

Am I missing a switch when running the install command above?

@mjcheetham
Copy link
Member

Regarding what you said about *nix above, if I use dnf or apt to install an application, the application is available for immediate use and doesn't require a new window. Are they doing something akin to what you suggest above?

I'd imagine that's because they are adding symlinks to a location already on the PATH, such as /usr/local/bin, so there is no need to update the PATH.

@nmat
Copy link

nmat commented May 21, 2020

Actually, I have installed vim, meld and a few other applications and rebooted my computer but still the commands are not available.

@trallnag
Copy link

trallnag commented Nov 3, 2021

Related #361

@aaronsteers
Copy link

aaronsteers commented Nov 25, 2021

After the Python installation wizard launched and finished, the tool reported: Successfully installed. But python was not automatically added to my path (reloading the session didn't help here, running $ python in the terminal takes me to the "Get Python" page in the Microsoft Store), though the python.exe was installed to the following location:

This is now a year later and it looks like winget install <python> is still broken. Am I missing a workaround? Do I need to open a ticket to the maintainers/repo of the Python package?

Reinstalling with the latest Python package (now 3.10) seems to get everything into PATH as expected! Not sure if the fix was within winget or within the Python package itself, but I am grateful for the fix regardless! For reference, I ran winget install Python.Python.3.

@Chris2011
Copy link

I have the same problem with GnuWin32.make. Successfully installation but it will not add make to the path automatically. It is seen in the list so it was installed. Is this now a thing, that needs to be changed in winget or in make itself to make this happen?

@aaronsteers
Copy link

@Chris2011 - While I can't give a definitive answer on this (I'm not a contributor or maintainer), I do think signs point to this being the responsibility of the package itself. So I think the action would be to go to the package maintainer and see about updating the install script for this package.

@Chris2011
Copy link

@aaronsteers ok, thx for your opinion :).

@nibanks
Copy link
Member

nibanks commented Nov 4, 2022

So I think the action would be to go to the package maintainer and see about updating the install script for this package.

Anyone know if there's an easy way to do this in a WiX installer?

@jazzdelightsme
Copy link
Member

This package may help:

winget install WingetPathUpdater
winget install github.cli
gh # <-- works!

It works by adding winget.cmd and winget.ps1 wrapper scripts, which handle updating the PATH for you.

See also: https://github.com/jazzdelightsme/WingetPathUpdater

@denelon denelon removed this from the Backlog-Client milestone Nov 14, 2024
nidietr-MSFT added a commit to nidietr-MSFT/winget-cli that referenced this issue Dec 10, 2024
0e27525d Bumping version to 1.1.0 (microsoft#222)
c639a506 Adding support for a custom proxy input (microsoft#218)
258d189b Improve logging when the content type is wrong (microsoft#221)
216210ab Adding required permissions to enable uploading of CodeQL results (microsoft#214)
fb953d6e Bump github/codeql-action from 2 to 3 (microsoft#215)
52af7124 Enabling CodeQL scanning (microsoft#211)
e555d764 Bump clang-format from 18.1.5 to 19.1.1 (microsoft#210)
ab8f0e72 Setup: improving build tools installation (microsoft#207)

git-subtree-dir: src/SfsClient/sfs-client
git-subtree-split: 0e27525d597c730e71646fd0b15bdc8c8503f24d
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Path Issue related to path environment variable Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests