Managing a local APT packages mirror with custom tags using aptly
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 15/100
- Issue 类型
- 文档
- 描述清晰度
- 需要澄清
- 活跃度
- 停滞
调研方向
The issue names aptly and apt-mirror but no source files, tests, or specific change. Start by reviewing aptly’s existing documentation for package tags and compare it with the requested client install workflow. Done would require clarifying whether this is a request for usage guidance or a product change and defining a concrete outcome.
由索引模型根据 Issue 内容生成。
描述
I'm looking for some advice and best practices on managing a local APT package mirror with custom tags.
Here’s the scenario I’m working with:
The Goal
I need to organize the packages on my local APT mirror with custom tags, allowing client machines to install packages based on these tags.
My Current Setup :
- Set Up the Local APT Mirror:
I'm using theapt-mirrorpackage to prepare a local APT Debian packages mirror. It has very simple configuration and is working
fine for me By using this local mirror, we are saving a lot of Internet bandwidth while installing multiple Debian clients in our network.
The Need for Tags
Now, we're looking to implement a Debian packages tagging approach. The idea is to assign tags to each Debian package and install them based on these tags. This would help streamline our installation process even further.
Exploring Aptly
I came across the aptly tool and it seems like it might solve this problem.
However, I am not entirely sure how to best implement this with Aptly, or if there are better approaches.
Questions :
- What are the best practices for managing and distributing package tags with Aptly?
- Are there any specific features in Aptly that support tagging and installing packages based on these tags?
I appreciate any insights, experiences, or recommendations you can share.
Thanks in advance for your help!
- 主要语言
- Go
- 星标
- 2.9k
- 派生
- 436
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aptly-dev/aptly 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 1/5 1 小时以内 新手友好度 80/100
-
难度 4/5 3-5 天 新手友好度 54/100
相似的 Issue
-
[doc-healer] DDUw improvement: retry integrity-filtered issue reads with direct single-item lookups未关闭automation documentation
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
bug needs-triage
难度 2/5 1-3 小时 新手友好度 80/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
containerd/containerd#14476 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 82/100
Infisical/infisical#8987 · 1 条评论 ·
维护者通常 1 天内回复
-
scan framework and scan control accept empty and whitespace-only policy names in Args validation可能已有人在做 @WKr1shna 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复