[RFC] Update-specific messages, and install-only INSTALL.msg
还没有人认领这个 Issue。
评估
调研方向
Start by tracing how INSTALL.msg is created and displayed, then inspect the xbps-create invocation and xbps-src package layout described in the issue. Determine how versioned UPDATE-.msg files could be stored and selected for update transactions, while keeping INSTALL.msg limited to fresh installs and reinstalls. Done means the behavior and required package changes are specified well enough to implement and test.
由索引模型根据 Issue 内容生成。
描述
As is currently stands, the only way to signal a breaking change in an update is to mention it in INSTALL.msg. This shows the message for any updates, and even for fresh installations. On top of that, messages relevant to only a fresh installation are shown for updates too.
The result is that most messages shown in an average transaction aren't relevant in any way to the transaction, which causes users to learn to tune out the messages.
I propose adding messages that are specific to an update (or rather, specific to a breaking change), and changing the existing INSTALL.msg to be only shown for fresh installs or reinstalls.
This would require storage of the update messages, along with the package version containing the breaking change. One such update message would only be shown if the package is being updated, and if the currently installed version is lower than the message's version. XBPS should be able to show as many update messages as relevant to a particular transaction.
The logic for when INSTALL.msg is shown would be changed to not show the message for updates.
I'm not familiar enough with XBPS internals to know what would need to change implementation-wise.
On xbps-src's end this would probably look like additional UPDATE-<ver>.msg files in a package's directory, along with changes in the xbps-create invocation. A good number of packages would need to be updated to use UPDATE messages.
EDIT: I realised a big flaw in my pick of what version should be recorded along with an UPDATE message, so I switched it to be the first version that breaks (message shows for any currently installed version lower than it).
- 主要语言
- C
- 星标
- 1.2k
- 派生
- 152
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
void-linux/xbps 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 68/100
void-linux/xbps#475 ·
-
难度 4/5 3-5 天 新手友好度 45/100
void-linux/xbps#701 ·
-
难度 4/5 3-5 天 新手友好度 55/100
void-linux/xbps#700 ·
-
xbps-query -RX repository overrides可能已有人在做 @outofsyncrs 于 35 天前认领。 未关闭bug
难度 3/5 1-2 天 新手友好度 45/100
void-linux/xbps#696 ·
-
难度 3/5 1-2 天 新手友好度 52/100
void-linux/xbps#695 · 7 条评论 ·
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
research-radar
难度 2/5 1-3 小时 新手友好度 63/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
-
"systemctl is-system-running --wait" may hang indefinitely for non-root users可能已有人在做 @alexonea 今天认领。 未关闭bug 🐛 systemctl
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
testing: DISK test reads the wrong directory entry offset on H89可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
FujiNetWIFI/fujinet-lib#115 · 1 条评论 ·
维护者通常 1 天内回复