You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
This improvement refers to an existing feature. If you want to suggest a new feature, please use this template.
This improvement is not a bug. If you want to report a bug, please use this template.
Describe the improvement
Currently the install options provides many options and allows you to modify the install location of the package. However, the one thing that it is missing is showing where that install location is to begin with. Currently, there are two provided options for the install location: select an install location and reset the install location. However, there is no clear indication where the default install location is. I would like to propose to show the default install location of the package within the install options.
Thank you.
Describe how this improvement could help users
The immediate improvement scenarios that come to mind are the following:
For new folks like me who don't know the install locations, it will now show the default install location.
For people like me who are coming from an existing package manager (eg. chocolatey) and are either updating or overriding/installing the same package but with another package manager.
For example, I previously had ffmpeg installed via chocolatey. It was out of date, but since then I had moved to WinGet via UniGetUI. Instead of updating or first removing chocolatey, I opted to install the latest ffmpeg from WinGet. So now I have two ffmpeg packages - one from chocolatey and one from WinGet. However, I'm not entirely sure if WinGet or UniGetUI realized that I had a previous install and decided to replace my existing ffmpeg binaries within my chocolatey/bin folder, or if it installed elsewhere.
Funny enough, I just tried where ffmpeg to see where it was installed and nothing was listed and nor was it in my PATH environment variable. The previous ffmpeg binary wasn't updated. So I have no idea where if it was in fact installed to even add it to my PATH manually.
When packages don't provide an installer or when an interactive installation doesn't prompt an install location (due to the installer?), it would be helpful to know again where it was installed to.
The text was updated successfully, but these errors were encountered:
For new folks like me who don't know the install locations, it will now show the default install location.
Most of the times, the default install location can't be obtained.
3. When packages don't provide an installer or when an interactive installation doesn't prompt an install location (due to the installer?), it would be helpful to know again where it was installed to.
When a package gets installed, you can right-click the installed package (on the installed packages list) -> Open install location
When a package gets installed, you can right-click the installed package (on the installed packages list) -> Open install location
This is embarrassing. Honestly, I had never noticed this option. Maybe it's because it was grayed out since as you said earlier most of the time the location can't be obtained. Although, I would appreciate if you could still see if it will be possible to always fetch the installed location of a package.
Please confirm these before moving forward.
Describe the improvement
Currently the install options provides many options and allows you to modify the install location of the package. However, the one thing that it is missing is showing where that install location is to begin with. Currently, there are two provided options for the install location: select an install location and reset the install location. However, there is no clear indication where the default install location is. I would like to propose to show the default install location of the package within the install options.
Thank you.
Describe how this improvement could help users
The immediate improvement scenarios that come to mind are the following:
chocolatey/bin
folder, or if it installed elsewhere.where ffmpeg
to see where it was installed and nothing was listed and nor was it in my PATH environment variable. The previous ffmpeg binary wasn't updated. So I have no idea where if it was in fact installed to even add it to my PATH manually.The text was updated successfully, but these errors were encountered: