On Tue, 13.01.15 10:43, Cosimo Cecchi (cosi...@gnome.org) wrote: > Hi all, > > I was wondering if there's any reason we typically don't install on the > system DBus XML interface files for services. On my system, I can see a > bunch of definitions in /usr/share/dbus-1/interfaces, but it's by no means > a complete list of all the services in the system.
Well, systemd at least used to install them, but we don't do this anymore, since there's really no clear consumer of it. Also, it's not clear how precisely to put them there. Most projects that put the files their, put a full descriptition of an object node there, which might have multiple interfaces. So you end up encoding multiple interfaces in a single file. But now, if you have 8 different interfaces, and use them in different combinations, what would you even place on disk? each interface only once? or every possible combination of interfaces (which would be highly redundant? We eventually decided to remove all this from systemd since this also created issues with cross-platform builds, since the introspection was created dynamically, and thus required built code to be executed to get them... I think it's probably a better idea to pull out the stuff from running daemons. Or, if you really want to keep the dir, then at least standaridze what should be in it, how the files are named, and such. AMong other things that means that it really should only include <interface>, but no <node> elements, if you follow what i mean... Lennart -- Lennart Poettering, Red Hat _______________________________________________ desktop-devel-list mailing list desktop-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/desktop-devel-list