Add support for installing via homebrew

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

The five steps span two repositories, so start by mapping this repo: the release/tag setup, the packaging config (pyproject/setup files), and the built-in updater's entry point that must detect a brew install and stand down. Then read the splunk/homebrew-tap repo structure and the Formula Cookbook links given in the issue to see what a formula and its sha256 pin require. Done means a formula exists in the tap, a GitHub Actions workflow updates its hash on each release, and brew upgrade alone drives updates for brew-managed installs.

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

描述

Add support for installing via homebrew, these are the high level things that will need to be done, from my understanding:

  1. Cut versioned releases/tags so a formula has something stable to pin (url+sha256); a head block can track main in the meantime.
  2. Allow brew to manage the update lifecycle — the built-in updater needs to detect/disable itself under a brew install and defer entirely to brew upgrade, or we'll have two update systems fighting.
  3. Host it in our splunk tap  https://github.com/splunk/homebrew-tap rather than homebrew-core first — core has strict stability/notability bars this project doesn't need to clear yet.
  4. Write the formula and commit to the splunk tap.
  5. Setup github actions to auto update the hashes in the splunk tap on each release.

Resources:

主要语言
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 摘要。