Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

repo reorg bikeshed

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
c
领域
cli, tooling

调研方向

Review the design questions in issue #573 and the related void-infrastructure pull request #142 before locating the relevant XBPS repository URL handling. Resolve the template delimiter, supported values, and architecture naming behavior with project guidance; done means those choices are agreed and implemented with appropriate validation.

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

描述

related to: https://github.com/void-linux/void-infrastructure/pull/142

@the-maldridge expressed interest in the new layout being .../<XBPS_ARCH>/..., and I think I agree that this would make the most sense.

I think the best way to implement this in xbps (and having the side benefit of preventing needing to -R other arch's repos when installing something for another XBPS_ARCH) would be to allow templating repo urls:

repository=https://repo-default.voidlinux.org/current/{{XBPS_ARCH}}/
  1. What delimiter characters should be used to template this? {{XBPS_ARCH}}, %XBPS_ARCH% were thoughts I had.
  2. should other templated values be allowed, like ARCH and LIBC?
  3. Could this also be an opportunity to change <arch> -> <arch>-glibc? <arch> would have to stick around as a legacy alias of course.

I am interested in implementing this once some of the details are hashed out

主要语言
C
星标
1.2k
派生
152
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

void-linux/xbps 的其他 Issue

查看 void-linux/xbps 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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