[BUG] bat is not in PATH after installing with winget

[NikGovorov]

What steps will reproduce the bug?

1. execute winget install sharkdp.bat
2. exit terminal
3. open terminal
4. run bat

What happens?

Actual result: bat.exe is not in PATH

What did you expect to happen instead?

Expected result: bat.exe is in PATH

~/AppData/Local/Microsoft/WinGet/Packages/sharkdp.bat_Microsoft.Winget.Source_8wekyb3d8bbwe is in PATH, but bat.exe is located in ~/AppData/Local/Microsoft/WinGet/Packages/sharkdp.bat_Microsoft.Winget.Source_8wekyb3d8bbwe/bat-v0.23.0-x86_64-pc-windows-msvc

How did you install bat?

winget install sharkdp.bat

bat version and environment
bat-v0.23.0
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22621 N/A Build 22621

[NikGovorov]

My account didn't have privileges to create symbolic links (i.e. Dev Mode was not enabled), so winget tried to add the package's root path to PATH instead of creating a symbolic link to the executable. But as the package does not have its binaries in the root, it didn't work (see the bug description). Ideally, the release workflow should zip all files without an extra bat-v0.23.0-x86_64-pc-windows-msvc subfolder to support systems with no elevated privileges or with no permission to create symbolic links. See https://github.com/ajeetdsouza/zoxide for an example.

[sharkdp]

@sitiom Notifying you, just in case you are interested.

[sitiom]

• Root directory of portable packages is always added to the PATH regardless of RelativeFilePath microsoft/winget-cli#2909

This should already be resolved in the latest release candidate build of Winget. For Winget bugs, you should be looking at the https://github.com/microsoft/winget-cli repo first.