microsoft / microsoft/winget-pkgs

[Package Issue]: GodotEngine.GodotEngine

Open
#174,625 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

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

Installed Godot using Winget. The associated executables are installed correctly; however, the links and command line aliases are not being created for the executable, and despite being found under winget list, I am not able to uninstall using winget (No installed package found matching input criteria.)

Steps to reproduce
  • In console running as administrator: winget install --id=GodotEngine.GodotEngine -e
  • Refresh/reopen console
  • Verify presence: winget list --id=GodotEngine.GodotEngine
  • Attempt command line aliases indicated by installation output
    • godot
    • godot_console
  • Attempt uninstall: winget uninstall --id=GodotEngine.GodotEngine
Actual behavior

Executables are installed in proper place. No links created in %LOCALAPPDATA%\Microsoft\WinGet\Links. PATH not updated to include %LOCALAPPDATA%\Microsoft\WinGet\Links. For some reason, %LOCALAPPDATA%\Microsoft\WinGet\Packages\GodotEngine.GodotEngine_Microsoft.Winget.Source_8wekyb3d8bbwe is added to my PATH.

Expected behavior

Executables installed in proper place. Links created in %LOCALAPPDATA%\Microsoft\WinGet\Links. As this is the first time I have installed using winget, I expect %LOCALAPPDATA%\Microsoft\WinGet\Links to be added to my path. Executables should be findable in start/search menu.

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

Windows: Windows.Desktop v10.0.22631.4169
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.23.1911.0

Winget Directories
------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputD…
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.js…
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

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

----------------------------------------------------------------------------------------
I have installed `winget` using the `winget-install` script available on Powershell Gallery.
Screenshots and Logs
wingetgodotissues

WinGet-2024-09-21-17-52-09.527.log

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 the installation and uninstall commands in the issue, then inspect the attached WinGet log and the reported Links, Packages, and PATH locations. Done means the Godot executables are discoverable through the expected aliases and the package can be found and uninstalled with the reported winget command.

Written by the indexing model from the issue text.

Assessment

Tech stack
godot
Domain
cli, operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.