Add support for installing via WinGet on Windows

Abierto
  • ¿Algo no está bien?
#73 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
powershell, python
Área
release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
146
Forks
34
Merge medio
14 h 35 min
PR fusionados (30 d)
64

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de splunk/token-meter

Todos los issues de splunk/token-meter

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.