[Package Issue]: SWIG.SWIG fails to setup aliases

[Wallby]

Please confirm these before moving forward

• I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
• I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue

Installation issue.

Brief description of your issue

Installing winget install SWIG.SWIG succeeds, but with output:

${\textsf{Found \color{cyan}SWIG \color{}[\color{cyan}SWIG.SWIG\color{}] Version 4.4.0}}$
${\textsf{This application is licensed to you by its owner.}}$
${\textsf{Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.}}$
${\textsf{Successfully verified installer hash}}$
${\textsf{Extracting archive...}}$
${\textsf{Successfully extracted archive}}$
${\textsf{Starting package install...}}$
${\textsf{\color{lightyellow}Path environment variable modified; restart your shell to use the new value.}}$
${\textsf{\color{lightyellow}Command line alias added: "ccache-swig"}}$
${\textsf{\color{lightyellow}Command line alias added: "swig"}}$
${\textsf{Successfully installed}}$

However, the only path added to the environment variable is %userprofile%\AppData\Local\Microsoft\WinGet\Packages\SWIG.SWIG_Microsoft.Winget.Source_8wekyb3d8bbwe\swigwin-4.4.0\CCache, but swig is one directory less deep (../)

So what does Command line alias added: "swig" mean? ccache-swig works, but swig not.

Steps to reproduce

Try to install SWIG.SWIG
Then try to run the aliases output

Actual behavior

swig alias doesn't work.
PATH user environment variable is set to CCache directory, in which swig.exe isn't.

Expected behavior

Perhaps both the root and CCache directory are added to the path?

Environment

Windows Package Manager v1.12.350
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.26200.7171
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.27.350.0

Winget Directories
-----------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\Diag…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\sett…
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
DefaultProxy                              Disabled

Screenshots and Logs

No response

[evilbananas]

This looks to be a bug with winget itself rather than an issue with the manifest. If you have multiple RelativeFilePath and one is in a different directory from the rest, it will only add the first one to the user's PATH.

Issue report that is similar in winget-cli: microsoft/winget-cli#5678