Portable/stand-alone executables

Open
#116 0 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
api

Research direction

Start by reviewing related issue #182 and the WinGet-CLI specification mentioned in the note. Then inspect the REST source schema and validation entry points for installer types and Command elements. Done means the published requirements are reflected and portable installers are limited to a single Command element.

Written by the indexing model from the issue text.

Description

Issue-Feature
Description of the new feature / enhancement

Related to:

Schema will be modified to support the installation of portable / stand-alone executables.

Proposed technical implementation details

Inclusion of an installer type (portable) validation that will limit the number of Command elements to a single entry.

Note:
Waiting for specification to be published at WinGet-CLI to finalize requirements.

Dominant language
C#
Stars
317
Forks
79
No merged PRs in 30d

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.

More from microsoft/winget-cli-restsource

All issues in microsoft/winget-cli-restsource

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.