Go to file
caio-volpato f5c0ba9da4 Fix script execution not being triggered
When installing a release, the script was not getting executed,
on software.log we couldn't see the script output.

This is happening because run-software-scripts bash script is called
as follows `run-software-scripts preinstall` (or postinstall).
The run-software-scripts looks for executable files within PATCH_SCRIPTDIR/$1
but PATCH_SCRIPTDIR wasn't defined anywhere so it couldn't find the scripts.

This fix declares the PATCH_SCRIPTDIR, so the scripts are found
and executed as expected.

The legacy implementation (sw-patch) has a very similar mechanism and the
PATCH_SCRIPTDIR properly declared
7847f7087e/sw-patch/bin/patch-functions (L15)

Another minor issue is that the run-software-scripts doesn't properly
report when there are no scripts, creating a false impression that
the script was executed.

Test Plan:
SUCCESS: preinstall and postinstall script execution is triggered properly.
SUCCESS: run-software-scripts <folder_name> properly logs when no scripts are present

Closes-bug: 2070391

Change-Id: I91f315d29171a19f9b5c8c09db7c40465dcb49b6
Signed-off-by: caio-volpato <caio.volpato@windriver.com>
2024-06-25 16:02:00 +00:00
2024-06-17 10:06:20 -03:00
2024-06-04 13:54:21 +00:00
2019-04-19 19:52:36 +00:00
2024-06-21 20:53:46 +00:00
2018-05-31 07:37:12 -07:00
2019-07-19 10:28:00 -04:00
2018-07-25 08:48:07 -05:00
2024-01-10 19:26:20 +00:00

stx-update

StarlingX Software Management

Description
StarlingX Installation/Update/Patching/Backup/Restore
Readme 19 MiB
Languages
Python 92.7%
Shell 5.9%
HTML 1%
Makefile 0.4%