lint: Add --fix
- 主要言語
- Rust
- スター
- 2.3k
- フォーク
- 230
- 平均マージ
- 3日 3時間
- マージ済み PR(30日)
- 36
説明
I really wanted to avoid bootc being involved in being a "build system" - we should clearly support multiple build systems.
Right now we have `bootc container lint` which is an optional thing to invoke as part of a build, and it has grown more and more checks. It's readonly today.
In this issue I propose adding `--fix` (much like `cargo clippy` and `cargo clippy --fix` etc.).
Some things like `/var/run` we could easily apply the fix for (delete the link and let it be created by systemd-tmpfiles) e.g.
## Fixing users and tmpfiles
In https://github.com/coreos/rpm-ostree/issues/5230 I was thinking about trying to split out rpm-ostree's code for dealing with `/var` -> tmpfiles.d into something that can be invoked in a bit more standalone fashion.
However if we have `--fix` here...I think we could consider moving the tmpfiles.d and sysusers.d handling into this project instead. It's clearly within our dependency set already.
Does anyone have opinions on this?
If we did things this way then what would happen is all the tmpfiles.d code would move into this project, and rpm-ostree would just call it.
コントリビューションガイド
調査の方向性
まず `bootc container lint` コマンドから始めて issue の議論を確認し、その後、`/var` の扱いに関するリンク先の rpm-ostree issue を読んでください。提案は `--fix` を追加することですが、範囲(個別の修正にするのか、tmpfiles.d と sysusers.d の扱いを bootc に移すのか)について、完了の定義を決める前に解決する必要があります。
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- rust
- 領域
- cli
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 停滞
- 明瞭さ
- 説明が足りない
- 初心者へのやさしさ
- 25/100