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

Feature request: option to generate a lastupdate file during aptly publish

未关闭
#1,229 2 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
go
领域
cli

调研方向

Start by locating the aptly publish implementation and its existing tests, then trace how a repository is re-published and where its published root is determined. Decide how the optional lastupdate behavior and file location fit the existing command options. Done means re-publishing can generate or update a timestamp file in the published repository, with tests covering the behavior.

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

描述

wishlist

Detailed Description

To keep traffic to a minimum some mirrors would like to have a lastupdate file with timestamp of latest repo update. The mirror can then check this file before rsync'ing.

Context

See for example lastupdate check in archlinux's repo sync template (not an apt repo, but principle is the same).

Possible Implementation

I'm not very fluent in golang, but seems to me like it should be possible to (optionally) generate or update a lastupdate file in repo root (or perhaps a configurable subfolder) every time repo is re-published. From shell we can run date +%s > /path/to/aptly/published/folder/lastupdate to generate a lastupdate file with timestamp.

Your Environment

主要语言
Go
星标
2.9k
派生
436
PR 合并指标
30 天内没有已合并 PR

环境准备

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

从这里开始

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

aptly-dev/aptly 的其他 Issue

查看 aptly-dev/aptly 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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