Re: Installing DBus interface files for services

On Mon, Feb 2, 2015 at 3:22 AM, Lennart Poettering <mztabzr 0pointer de> wrote:
Oh no, that's not what I meant. I was more proposing to pull them
once, while you develop your stuff, and then shipping them in your own
tarball. So, don't pull them dynamically when you start building, but
you keep your own copy of the XML bits of other APIs, frozen and
stable in time in your own project.

That's what some modules are doing today already, but I don't think it really addresses my use case.
I would like to be able to easily build client code that interacts with a DBus service on the system without manually hunting for that interface from the service's git repository, ideally with a nice autotool integration like Philip proposed at the beginning of this thread.

So it seems that if we were to do that we're saying:
- services should install one of those files for each interface
- such files should have the same name as the interface and not contain other nodes
- tooling would verify that the above two are true?
- it wouldn't be a great idea to use this for clients that ends up exposing the generated code through a public API

Lennart, you also mentioned about cross-build problems, but I'm not really sure what those would be with this proposal - could you expand on that?


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]