Add support for installing via Scoop on Windows

未关闭
#72 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
55/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
python, shell
领域
release

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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.

主要语言
Python
星标
146
派生
34
平均合并
14 小时 35 分钟
30 天内合并 PR
64

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

splunk/token-meter 的其他 Issue

查看 splunk/token-meter 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。