summaryrefslogtreecommitdiffstats
path: root/scripts/pybootchartgui/pybootchartgui.py
diff options
context:
space:
mode:
authorWeisser, Pascal.ext <Pascal.Weisser.ext@karlstorz.com>2025-07-22 13:32:50 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2025-07-28 14:51:50 +0100
commit78f97b876219114b5144e691d4558adb44da46f3 (patch)
treec047324621e20a75150098f8c28031e1b18291a2 /scripts/pybootchartgui/pybootchartgui.py
parent6003a9615dc4cc8b02912815a3d785299d01fe25 (diff)
downloadpoky-78f97b876219114b5144e691d4558adb44da46f3.tar.gz
dbus: add traditional-activation PACKAGECONFIG
Add traditional-activation PACKAGECONFIG to DBus recipe in order to allow users to enable or disable traditional DBus service activation. DBus service activation refers to automatically starting an application when a DBus message is sent to a service provided by that application. Traditionally, this is done by the DBus-daemon, thus, the term traditional here. On systems using systemd, systemd can do this, instead. On some systems it might be of interest to disable the traditional service activation in order to ensure that services are always started via systemd. Per default, traditional service activation is enabled for DBus. Thus, the traditional-activation PACKAGECONFIG is added to the default PACKAGECONFIG. Otherwise, we might introduce a breaking change here. The binary dbus-daemon-launch-helper isn't created in case DBus is built with traditional service activation disabled, so we change its attributes only when traditional service activation is turned on. (From OE-Core rev: 272aafbf0a2a1a158fdff42b6ce295fe861f1327) Signed-off-by: Weisser, Pascal <pascal.weisser.ext@karlstorz.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/pybootchartgui/pybootchartgui.py')
0 files changed, 0 insertions, 0 deletions