rpm: evaluate uses of `%license` macro

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
47/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
dockerfile
领域
release

调研方向

Start with the Compose plugin spec linked in the issue and compare its %license entry with the other RPM spec files in the repository. Check RPM packaging behavior for license files and whether the other packages handle them implicitly; the work is done when the need for additional %license entries is established and any required changes are covered.

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

描述

We currently only use it in a single package; do we need to do so for other packages, or is it implicit / automatic?

One thing we should also look into; I noticed that we add an explicit %license macro for the Compose plugin docs;
https://github.com/docker/docker-ce-packaging/blob/e47d6372bc61efecd4ee9c3ff420d09798b0cad6/rpm/SPECS/docker-compose-plugin.spec#L50-L51

But we don't do this for other packages. It's possible that (given the standard naming used) this happens automatically, but perhaps we should look if additional things should be added.

Originally posted by @thaJeztah in #1112

主要语言
Dockerfile
星标
37
派生
42
平均合并
16 小时 53 分钟
30 天内合并 PR
30

环境准备

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

从这里开始

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

docker/packaging 的其他 Issue

查看 docker/packaging 的全部 Issue

相似的 Issue

更多 Release Issue

把新 issue 发到你的邮箱

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