Add support for installing via WinGet on Windows

Aperta
  • Qualcosa non va?
#73 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
powershell, python
Ambito
release

Direzione di ricerca

Start from the Windows bootstrap path referenced in the issue and the built-in updater that must defer to winget upgrade; compare sibling issues #71 (Homebrew) and #72 (Scoop) to see which distribution channel maintainers pick. Work spans producing a versioned artifact with SHA-256, a manifest PR to microsoft/winget-pkgs, and uninstall/startup ownership checks. Done means the manifest and installer contracts validate and Windows-native install/upgrade/uninstall passes on a clean host — validation the payload notes is not yet available.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Windows bootstrap currently uses WinGet only to acquire missing Git and Python prerequisites. Token Meter itself is not available through winget install.

This is one packaging option alongside Homebrew support and Scoop support. Maintainers should choose the supported distribution channel or channels; this issue does not request a preference or commitment to ship every option.

Proposed behavior

  1. Publish a versioned Windows distributable with an immutable download URL and SHA-256 checksum suitable for a WinGet manifest. The artifact format and release process should be selected by maintainers.
  2. Add a token-meter manifest to microsoft/winget-pkgs, or to another maintainer-selected repository if that is the accepted publication path.
  3. Declare the supported runtime prerequisites in the manifest and retain a per-user installation with no administrator requirement.
  4. Make the installed lifecycle package-aware: winget upgrade owns Token Meter updates. A WinGet-installed runtime must not also fetch, fast-forward, or reinstall itself through the built-in updater.
  5. Preserve the local-only server and Windows notification-area behavior. Uninstall must remove only Token Meter resources it owns, including its current-user startup entry and managed runtime, while preserving user session evidence and unrelated dependencies.
  6. Document the selected WinGet install, update, and uninstall flow beside the existing Windows bootstrap path.

Validation

  • Add manifest and installer contracts for the versioned URL, checksum, declared dependencies, per-user paths, update ownership, and uninstall ownership.
  • On a clean Windows host, validate installation through WinGet, readiness at /health and /menubar, current-user startup, winget upgrade, and uninstall.
  • Windows-native WinGet validation is pending. macOS source checks do not prove WinGet, PowerShell, registry-startup, or notification-area behavior.

No dashboard UI addition or privacy-boundary change is intended.

Lingua principale
Python
Stelle
146
Fork
34
Merge medio
14h 35m
PR unite (30g)
64

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di splunk/token-meter

Tutte le issue di splunk/token-meter

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.