Update registry metadata for portable packages updated outside of WinGet.

未關閉
#6,479 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
30/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
活躍
技術堆疊
cpp
領域
cli

研究方向

首先追蹤 WinGet CLI 的升級流程,以及它如何讀取和更新 portable package 的登錄檔中繼資料。檢視此流程如何比較已安裝版本與存放庫版本,然後找出現有的錯誤條件和相關測試。完成此項工作需要就外部更新的 portable package 的行為達成共識,並加入涵蓋範圍以避免錯誤降級或升級迴圈。

由索引模型根據 Issue 內容生成。

描述

Command-Upgrade Issue-Feature Portable
Relevant area(s)

WinGet CLI

Description of the new feature / enhancement

Some "portable" packages have their own internal "update" mechanism. If they get updated, and they were installed by WinGet, the registry metadata doesn't get updated.

This could lead to undesired behavior.

WinGet thinks the package is out of date and needs to be updated.

  • This could be turned into a no-op. If the latest version WinGet knows about matches the installed version, WinGet could update the metadata during the "upgrade" flow.

  • This could lead to a bad outcome if a newer version is installed than what WinGet is aware of and could lead to an upgrade loop in WinGet. This may justify a new "error condition" because WinGet doesn't know how to reason about the installed version. It could also have the "unintended" behavior of installing an older version of the package and clobber the newer one that was installed on the device.

Ideally, the latest version would be available in the WinGet repository, or the portable package could leverage WinGet to handle the upgrade flow to keep the registry metadata in sync. Otherwise, it would be good for the package to distribute an installer rather than a "bare portable executable".

Tools like the Windows App CLI can help build an MSIX packaged application including the binary. This is the ideal case in terms of package management, as Windows understands how to handle the situation, and WinGet isn't trying to keep the registry metadata in sync.

Optionally there are a large number of other supported installer technologies that can be used to build installers.

Proposed technical implementation details

No response

主要語言
C++
星號
26.6k
分支
1.8k
平均合併
3 天 10 小時
30 天內合併 PR
41

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

microsoft/winget-cli 的其他 Issue

查看 microsoft/winget-cli 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。