Add support for installing via Scoop on Windows

Aperta
  • Qualcosa non va?
#72 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
55/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python, shell
Ambito
release

Direzione di ricerca

Start from the existing Windows PowerShell bootstrap and its installer contract tests to see how install, update ownership, startup entry and uninstall are currently handled, plus how the built-in self-updater detects its runtime. Check whether the repo already cuts versioned GitHub releases/tags (referenced against #71 for the Homebrew equivalent). Done looks like: a token-meter Scoop manifest pinned to a versioned URL with SHA-256 and declared prerequisites, contract tests covering per-user paths, update ownership (Scoop-owned installs skip the self-updater) and uninstall ownership, and install/update/uninstall docs beside the Windows bootstrap section; note Windows-native validation is required.

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

Descrizione

Windows users can currently install Token Meter through the PowerShell bootstrap, which uses WinGet for prerequisites. Scoop users need a package-managed path with a stable artifact and one clear owner for updates.

Related: #71 proposes the equivalent Homebrew work.

Proposed behavior

  1. Cut versioned GitHub releases/tags so a Scoop manifest can pin a stable archive URL and SHA-256 checksum. Do not have the manifest track main.
  2. Publish a token-meter Scoop manifest in a Splunk-managed bucket, or document the selected bucket before adding the manifest.
  3. Declare the supported runtime prerequisites in the manifest. Installation must remain per-user, require no administrator access, and preserve the existing Windows local-only server and notification-area behavior.
  4. Make the Scoop installation lifecycle package-aware: scoop update token-meter owns application updates. A Scoop-installed runtime must not also fetch, fast-forward, or reinstall itself through the built-in updater.
  5. Ensure uninstall removes only Token Meter resources it owns, including its current-user startup entry and managed runtime, without removing user session evidence or unrelated Scoop-managed dependencies.
  6. Document the Scoop install, update, and uninstall flows alongside the existing Windows bootstrap path.

Validation

  • Add manifest and installer contracts covering the versioned URL, checksum, dependencies, per-user paths, update ownership, and uninstall ownership.
  • On a clean Windows host, validate scoop install token-meter, launch/readiness (/health and /menubar), current-user startup, scoop update token-meter, and scoop uninstall token-meter.
  • Windows-native Scoop validation is pending; macOS source checks do not prove PowerShell, Scoop, 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.