microsoft / microsoft/winget-pkgs

[New Feature]: Manifest handling for installed additional components

Open
#68,136 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description of the new feature/enhancement

Some installers install additional components that should be maintained updated (and uninstalled) separately afterwards.

In the screenshot from @ItzLevvie below (see https://github.com/microsoft/winget-pkgs/pull/68036#issuecomment-1200440331 for details) you can see an umbrella installer that installs multiple subcomponents:
image

Issues now:

  • Uninstalling the "umbrella" package will not remove the installed components
  • the proposed Package Identifier is incorrect e.g. for Torpedo Remote. It should be TwoNotes.TorpedoRemote instead of Remote5
  • I wanted to create a separate manifest for Torpedo Remote because it is updated separately from the driver umbrella package (via https://www.two-notes.com/en/torpedo-series/torpedo-remote/)

Is there a way to tell winget that it should recognize these as being described in other manifests?

Proposed technical implementation details (optional)

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

The issue names no files, tests, or entry points. Start by tracing how winget manifests represent umbrella installers and separately updated components, then define how package identifiers and relationships should be recorded. Done means the umbrella package can recognize, update, and uninstall its additional components through their separate manifests.

Written by the indexing model from the issue text.

Assessment

Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.