GTK Config Module uses XSettingsd to apply settings to GTK applications
on the fly, thus making it an optional runtime dependency. To provide
this information to distributions this patch is made.
BUG: 418263
FIXED-IN: 5.18.3
GTK Config Module uses XSettingsd to apply settings to GTK applications
on the fly, thus making it an optional runtime dependency. To provide
this information to distributions this patch is made.
BUG: 418263
FIXED-IN: 5.18.3
-- The following RUNTIME packages have not been found: * XSettingsd, XSettingsd daemon Allows GTK Config kded module to apply settings to GTK applications on the fly
No Linters Available |
No Unit Test Coverage |
Buildable 18822 | |
Build 18840: arc lint + arc unit |
I think you would want to make that a RUNTIME dependency. This stuff is mostly for packagers, telling them to install something isn't what we want.
I guess he refers to:
https://cmake.org/cmake/help/latest/module/FeatureSummary.html#command:set_package_properties
But seems, this only applies to dependencies checked by find_package().
I'm confused.
Does it mean, I should create custom FindXsettingsd.cmake module for xsettingsd, then write something like this:
find_package(Xsettingsd) set_package_properties(Xsettingsd PROPERTIES TYPE RUNTIME DESCRIPTION "Provides settings to X11 applications via the XSETTINGS specification" URL "https://github.com/derat/xsettingsd" )
?
Yes. Maybe you can take inspiration from this commit:
https://cgit.kde.org/kinfocenter.git/commit/?id=35b19106c5cb64c4705a3682269826d4be6510f2
BUG: 418263
This bug is not fixed by this patch. xsettingsd needs to be started in plasma-workspace/startkde/startplasma.cpp (or by systemd in the future).
FIXED-IN: 5.19
I would be nice, if this could make it to 5.18, so that xsettingsd would end up on the Kubuntu 20.04 ISO image (https://phabricator.kde.org/T12753).
xsettingsd is started by the daemon itself, if it's not instantiated already. The daemon itself launches at startup, because it is a kded module.
You are right, sorry for the noise! I must have mixed up someting while testing it on the Kubuntu 20.04 preview.
Ok. So, can I land it or should I wait for other reviewers? Also, should I make the dependency REQUIRED or leave it optional?
I don't think this is adding a new dependency just highlighting that there is one, so it's good to add to stable branches