microsoft / microsoft/winget-pkgs

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

Open
#322,180 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug Needs-Triage
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
616

Description

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] 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

```raw
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_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing `winget install SWIG.SWIG`, then try both reported aliases and compare the user PATH with the location of `swig.exe`. Trace the package's installation and alias configuration; done means installing the package makes `swig` work as the installer output claims.

Written by the indexing model from the issue text.

Assessment

Domain
cli, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.