Skip to content

Improved architecture handling #276

@denelon

Description

@denelon

Description of the new feature / enhancement

Some packages offer a different "latest" version of an application based on the architecture supported.

When the WinGet client is communicating with a REST endpoint the communications should be optimized to deal with different versions for different architectures.

The default flow should provide a better customer experience for both the "install" and "upgrade" scenarios.

When a specific architecture is specified using arguments, the response should honor the architecture specified.

When the "download" flow is being used, there should be an affordance to download the latest versions for "all" architectures.
There may also be caveats when a specific version is requested as opposed to just the "latest" version.

Proposed technical implementation details

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-FeatureComplex enough to require an in depth planning process and actual budgeted, scheduled work.

    Projects

    Status

    To Do

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions