From: Zhihang Wei <wzh@ilbers.de>
To: Kasturi Shekar <kasturi.shekar@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v1 0/2] installer: split backend APIs from frontend UI
Date: Wed, 4 Feb 2026 16:51:25 +0100 [thread overview]
Message-ID: <31bc8b58-8038-4872-be1c-7efa75e63365@ilbers.de> (raw)
In-Reply-To: <20260119055335.1006446-1-kasturi.shekar@siemens.com>
Applied to next, thanks.
Zhihang
On 1/19/26 06:53, 'Kasturi Shekar' via isar-users wrote:
> 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
>
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/31bc8b58-8038-4872-be1c-7efa75e63365%40ilbers.de.
next prev parent reply other threads:[~2026-02-04 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 5:53 'Kasturi Shekar' via isar-users
2026-01-19 5:53 ` [PATCH v1 1/2] installer: introduce sys_api.sh backend interface 'Kasturi Shekar' via isar-users
2026-01-19 5:53 ` [PATCH v1 2/2] installer-ui: use sys_api backend for frontend dialogs 'Kasturi Shekar' via isar-users
2026-02-04 15:51 ` Zhihang Wei [this message]
2026-02-05 6:53 ` [PATCH v1 0/2] installer: split backend APIs from frontend UI 'Jan Kiszka' via isar-users
2026-02-05 8:47 ` Zhihang Wei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=31bc8b58-8038-4872-be1c-7efa75e63365@ilbers.de \
--to=wzh@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=kasturi.shekar@siemens.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox