mbox series

[v3,0/4] installer: separate installer into backend, UI, and flow modules

Message ID 20260608051737.946413-1-kasturi.shekar@siemens.com
Headers show
Series installer: separate installer into backend, UI, and flow modules | expand

Message

Kasturi shekar June 8, 2026, 5:17 a.m. UTC 
From: Kasturi Shekar <kasturi.shekar@siemens.com>

This series refactors the installer by separating backend logic,
attended UI, and high-level flow into dedicated modules.
The main objectives are:
 - improve readability and maintainability
 - keep behavior and user-visible flow unchanged

Patch-1: introduces a backend API layer (sys_api.sh) that provides
installer functionality via structured shell functions.

Patch-2: adapts the existing dialog-based installer frontend to consume
these APIs, without changing behavior.

Patch-3: high-level orchestration and keep deploy-image-wic.sh as a thin launcher.
This keeps the externally used script name stable while making the flow easier
to review and maintain.

patch-4: update deploy-image recipe to ship the newly split installer modules

 .../deploy-image/deploy-image_0.1.bb          |   6 +-
 .../files/usr/bin/deploy-image-wic.sh         | 472 +++++++-----------
 .../files/usr/bin/installer_ui.sh             | 217 +++++---
 .../deploy-image/files/usr/bin/sys_api.sh     | 400 ++++++++++++---
 4 files changed, 688 insertions(+), 407 deletions(-)
 mode change 100755 => 100644 meta-isar/recipes-installer/deploy-image/files/usr/bin/deploy-image-wic.sh
 mode change 100755 => 100644 meta-isar/recipes-installer/deploy-image/files/usr/bin/installer_ui.sh