From db2baa03bb34a45b4d4b8f13ea50d4f4d193e6c1 Mon Sep 17 00:00:00 2001 From: ScottW514 Date: Mon, 24 Aug 2026 16:04:09 -0400 Subject: [PATCH] dev image: keep nano by re-setting the removal list IMAGE_INSTALL:remove applies after every append, so the release recipe's removal of nano also stripped it from the dev image that appended it back. The dev recipe now re-sets the removal list to gfui-client alone. No catalog consequence: dev image composition only. --- .../recipes-forgefirm/images/forgefirm-image-dev.bb | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/meta-forgefirm/recipes-forgefirm/images/forgefirm-image-dev.bb b/meta-forgefirm/recipes-forgefirm/images/forgefirm-image-dev.bb index 7ca509f..69f7e87 100644 --- a/meta-forgefirm/recipes-forgefirm/images/forgefirm-image-dev.bb +++ b/meta-forgefirm/recipes-forgefirm/images/forgefirm-image-dev.bb @@ -12,9 +12,14 @@ IMAGE_INSTALL += " \ forgetest \ python3-gfutilities-emulator \ htop \ - nano \ " +# The release recipe removes nano from the shared base list (bench +# convenience, 8.7 MB with libmagic). A removal applies after every append, +# so the dev image re-sets the removal list to keep nano instead of adding +# it back. +IMAGE_INSTALL:remove = "gfui-client" + # debug-tweaks (passwordless root, root SSH login) belongs ONLY to the dev # image - never the release image. It lives here, not in the shared kas # local.conf, so the release forgefirm-image cannot inherit it.