lint: Add --fix
- Langage dominant
- Rust
- Étoiles
- 2.3k
- Forks
- 230
- Merge moyen
- 3 j 3 h
- PR mergées (30 j)
- 36
Description
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.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par la commande `bootc container lint` et examinez la discussion de l’issue, puis lisez l’issue rpm-ostree liée concernant la gestion de `/var`. La proposition consiste à ajouter `--fix`, mais le périmètre — corrections individuelles ou déplacement de la gestion de tmpfiles.d et sysusers.d dans bootc — doit être tranché avant de pouvoir définir ce qui constitue l’achèvement du travail.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- rust
- Domaine
- cli
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100