consolidation of *-dbus-interfaces

[Lei YU]

On Sat, Oct 26, 2019 at 3:18 AM Brad Bishop <bradleyb at fuzziesquirrel.com> wrote:
>
> Hi everyone
>
> I’ve discussed with a couple people off list the idea of consolidating all the dbus interfaces into a single repository.  Today there exist four:
>
> phosphor-dbus-interfaces
> openpower-dbus-interfaces
> ibm-dbus-interfaces
> intel-dbus-interfaces
>
> The idea is that going forward all dbus interfaces would just go in phosphor-dbus-interfaces regardless of the namespace.  That should cut away a lot of complexity in the bitbake metadata and in other places as well.
>

That's great and I would love to see this happen!

> Is there any opposition to this idea?  If anyone is worried about maintainer-ship, I am working on deploying the owners file plugin on our Gerrit install which enables kernel style ownership of different files depending on path, regex matches, etc.
>
> I would guess there would be a desire to configure (as in autoconf) in or out different namespaces.  Am I correct in that thinking?  Any thoughts on how exactly that should be done?

I guess package config seems like a way to configure which parts to build.

>
> On a somewhat related note I tried migrating phosphor-dbus-interfaces build to meson and failed miserably when I got to generated sdbus++ header file placement.  If anyone has any ideas on how to do that I’d love to hear about it.

I am OK to keep the existing autoconf tools as it works well.
For meson, I am not sure what kinds of issues you meet, but we
probably need to write configs to generate all kinds of server.hpp/cpp
files by `run_command()`