winget-pkgs #

A personal winget source for the Windows programs Jeff writes: the manifests that describe each release, and the static site that winget reads them from.

Language #

Program: A piece of software Jeff writes and releases from its own repository. Avoid: App, project, tool

Package: A program as winget sees it, named by its package identifier and made up of one or more versions. Avoid: Program (when meaning the winget entry), app

Package identifier: The permanent <Publisher>.<Package> name winget uses to find, install and upgrade a package. Avoid: Package ID, app ID, name

Publisher: The first segment of every package identifier in this source; there is exactly one, and it is Jeff. Avoid: Author, vendor, owner

Manifest: The set of YAML files that describe one version of one package: its version file, its installer file and its default locale file. Avoid: Spec, package file, recipe

Manifest repository: The git repository holding every manifest, laid out the way Microsoft's winget-pkgs is. Avoid: Package repo, winget repo, the repo

Submission: A pull request against the manifest repository that adds a manifest for a new version of a package. Avoid: Update, upload, release

Submitter: The forge user that opens submissions on a program's behalf; it can propose versions but never merge them. Avoid: Bot, robot, CI user

Release: A tagged, non-prerelease version of a program, whose installers are attached to it on the forge. Avoid: Build, prerelease, version (when meaning the forge object)

Installer: The file a manifest points winget at to install one version of a package on one architecture. Avoid: Binary, asset, download

Source: The static site winget is told about with winget source add, generated from the manifest repository after each merged submission. Avoid: Static site, website, feed, repository

Source name: The name a Windows machine knows the source by, given to winget source add -n. Avoid: Source ID, remote

Index: The searchable catalogue of every package version in the source, shipped to clients as a signed package. Avoid: Database, catalog, source.msix (when meaning the concept)

Signing certificate: The one certificate the index is signed with, which every client must trust before the source can be added. Avoid: Code signing key, CA, cert