Rename image to monolith-gnome for multi-edition prep#11
Merged
Conversation
Rename the recipe and published package from monolith to monolith-gnome so additional desktop editions (KDE, COSMIC, niri, ...) can live in this repo as separate recipes, per BlueBuild's multiple-images layout. - recipes/recipe.yml -> recipes/recipe-gnome.yml; name: monolith-gnome - os-release: PRETTY_NAME=Monolith GNOME, VARIANT=GNOME, VARIANT_ID=gnome; NAME=Monolith and ID=monolith kept as the shared family identity - build matrix, release + PR-rebase workflows, README, and changelog help text point at monolith-gnome / recipe-gnome.yml Brand-level names (hostname, firstboot-label service, dconf dbs, gschema override, fastfetch logo, Ptyxis profile) are left as monolith since they are shared across all future editions.
🧪 Test this PR on a real installOnce the build check on this PR passes, a signed test image is published to rpm-ostree rebase ostree-image-signed:docker://ghcr.io/mondrethos/monolith-gnome:pr-11-44
systemctl rebootThe tag is rebuilt on every new commit here, so rpm-ostree rebase ostree-image-signed:docker://ghcr.io/mondrethos/monolith-gnome:latestThe test tag stops updating once this PR is merged or closed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
First step toward hosting multiple desktop editions (KDE, COSMIC, niri, …) from this repo. Per BlueBuild's multiple-images layout, each edition is its own
recipe-<edition>.ymlwith a distinctname:, so the existing image is renamedmonolith→monolith-gnome.Scope is the rename + repointing only; factoring shared modules into
from-fileincludes and adding other editions/NVIDIA variants come later.Changes
recipes/recipe.yml→recipes/recipe-gnome.yml;name: monolith-gnome(publishesghcr.io/mondrethos/monolith-gnome)PRETTY_NAME=Monolith GNOME,VARIANT=GNOME,VARIANT_ID=gnome;NAME=MonolithandID=monolithkept as the shared family identitymonolith-gnome/recipe-gnome.ymlBrand-level names (hostname, firstboot-label service, dconf dbs, gschema override, fastfetch logo, Ptyxis profile) are left as
monolith— shared across all future editions.Note on merge
This renames the published package, so it's a new image path. The first build on
mainpublishes…/monolith-gnome;…/monolithstops updating. Existing installs need a one-timerpm-ostree rebaseonto the new path (README updated accordingly).