mbox series

[v1,0/2] installer: split backend APIs from frontend UI

Message ID 20260119055335.1006446-1-kasturi.shekar@siemens.com
Headers show
Series installer: split backend APIs from frontend UI | expand

Message

Kasturi Shekar Jan. 19, 2026, 5:53 a.m. UTC 
This patch series is a first step towards splitting the installer into
a reusable backend and a frontend.

Patch-1: introduces a small backend API layer (sys_api.sh) that provides
installer functionality via structured shell functions with JSON-style
return values.

Patch-2: adapts the existing dialog-based installer frontend to consume
these APIs, without changing behavior. This serves as validation that
the abstraction is sufficient for the current UI.

Further steps (not included here) would build additional frontends on
top of the same backend APIs, but this series focuses purely on the
foundation and existing workflow.

please refer to the initial discussion here
[1]https://groups.google.com/g/isar-users/c/Uy3Mg9gJnA4

Kasturi Shekar (2):
  installer: introduce sys_api.sh backend interface
  installer-ui: use sys_api backend for frontend dialogs

 .../files/usr/bin/installer_ui.sh             | 86 +++++++++++++++++++
 .../deploy-image/files/usr/bin/sys_api.sh     | 84 ++++++++++++++++++
 2 files changed, 170 insertions(+)
 create mode 100755 meta-isar/recipes-installer/deploy-image/files/usr/bin/installer_ui.sh
 create mode 100644 meta-isar/recipes-installer/deploy-image/files/usr/bin/sys_api.sh