I think this bug is about the interface files, not the policy files. Not easy to track because the link to mender-client.in in the description is not versioned, and today's master L350 has moved.
The policy files were already conditionally installed, so I am working on conditionally install the interface files too.
Lluis CamposJuly 19, 2021 at 1:22 PM
Estimated to 3SP
eystein.maloy.stenbergJuly 7, 2021 at 4:32 PM
OK! Could someone provide an estimate please?
Lluis CamposJuly 7, 2021 at 6:51 AM
@eystein.maloy.stenberg yes, it should be backlogged. I also moved it into a bug instead of a task.
Based upon the discussion here: https://northern-tech.slack.com/archives/C2D3HRU9M/p1624885215001500
It was discovered that the D-Bus policy files are unconditionally installed no matter if D-Bus is support is compiled into the client or not.
See this: https://github.com/mendersoftware/meta-mender/blob/dunfell/meta-mender-core/recipes-mender/mender-client/mender-client.inc#L350
Acceptance criteria:
Only install the D-Bus policy files if D-Bus support is enabled in the client
Acceptance test to cover the above condition