Decide where a package, app, or command belongs — dnf5 at build time, Homebrew, Flatpak, or ujust — and how each is validated. Use when adding or removing something from the image.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
| The thing is… | Put it in | Installed |
|---|---|---|
| A system package the image needs to boot or run | build/20-packages-and-services.sh | at build time |
| A CLI tool a user chooses to have | custom/brew/*.Brewfile | on demand, by the user |
| A GUI application | custom/flatpaks/*.preinstall | on first boot |
| A command that configures the system | custom/ujust/*.just | available from first login |
| A system file: unit, preset, tmpfiles.d | custom/files/ | at build time |
| Per-user config for new accounts | custom/config/ | at build time, into /etc/skel |
The dividing line is who decides and when: build time for what the image must have, runtime for what the user chooses.
build/20-packages-and-services.sh. Use dnf5, always with -y, and disable
any repository you enable. build/README.md has the
phase map.
Prefer a package the base already ships. When a COPR is unavoidable,
copr_install_isolated enables and disables it for you.
Brewfiles in custom/brew/, plus a ujust recipe so users install it by name.
custom/brew/README.md has the format.
Preinstall declarations in custom/flatpaks/. The app must exist on Flathub;
just validate-flatpaks checks.
custom/flatpaks/README.md has the format and
the first-boot behaviour.
Recipes in custom/ujust/. No dnf5 or rpm — the image is immutable.
custom/ujust/README.md has the recipe shape.
custom/files/ mirrors /; custom/config/ seeds /etc/skel/.config/. Each
directory's README has the semantics.
The reverse of adding: delete the line or the file, then check nothing still
references it. A package removed from the package phase may still arrive as a
dependency or from an overlay; bootc container lint and the image build catch
the obvious cases.
just validate-brewfiles
just validate-flatpaks
just check
just build
CI runs validate-brewfiles, validate-flatpaks, and validate-justfiles on
every pull request.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
GitHub Actions, Renovate, the two-branch release model, signing, and promotion. Use when changing workflows, dependency policy, or releasing.
The English summary is being prepared. Showing the original description.
Bootstrap a new image from this template: rename the project, enable Actions and Renovate, protect the branch, and reach a first green build. Use when forking the template or when setup has stalled.
The English summary is being prepared. Showing the original description.
Architecture, repository layout, and file map for this template. Use when orienting to the repository, tracing how the image is assembled, or deciding which skill covers a task.
The English summary is being prepared. Showing the original description.
Symptom to cause to fix for build, CI, and runtime failures, plus the pre-commit checklist. Use when something is broken or before opening a pull request.
The English summary is being prepared. Showing the original description.