Re: [systemd-devel] Can apps ship their own copy of libudev?

binary compatibility. It's just annoying when it happens... -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ systemd

Re: [systemd-devel] Can apps ship their own copy of libudev?

. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center signature.asc Description: This is a digitally signed message part. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http

Re: [systemd-devel] Can apps ship their own copy of libudev?

that the code you wrote above (dlopen-dlsym-call, plus handling dlopen failing) is worse than the equivalent solution generated by the linker and dynamic linker for the case when we are allowed to link directly. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open

Re: [systemd-devel] [HEADSUP] libsystemd-bus + kdbus plans

to avoid it entirely. The userspace part for setting up the busses will live in systemd. kdbus is not going to be available for non-systemd systems unless somebody sits down and writes an entirely independent bus userspace. kdbus is entirely different from AF_BUS. == -- Thiago Macieira - thiago

Re: [systemd-devel] Compatibility between D-Bus and kdbus

it reads DBusDBus, but on little-endian systems it actually reads suBDsuBD :-) Not relevant, though. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1

Re: [systemd-devel] Compatibility between D-Bus and kdbus

also be mandatory. Yes, they are mandatory. process credentials might be suppressed hwover, for example if they cannot be translated due to namespaces. Thanks. Could you clarify in the docs? -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open

Re: [systemd-devel] Compatibility between D-Bus and kdbus

of expect that the normal case is that the policy applies to the entire tree, not just one more level. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1

Re: [systemd-devel] Compatibility between D-Bus and kdbus

applicable for and when you should avoid it. In this specific case, precision is not required, as a 25-second timeout is really long. Currently, QtDBus on dbus1 may get that wrong for as much as one full second (less than 5% error). -- Thiago Macieira - thiago (AT) macieira.info - thiago

Re: [systemd-devel] Compatibility between D-Bus and kdbus

the other way round. Fair enough. I guess that, if needed, you'll make the full hierarchy wildcard a double asterisk, e.g. org.example.**. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center PGP/GPG: 0x6EF45358

Re: [systemd-devel] Compatibility between D-Bus and kdbus

app needs to know about kdbus too. So we have a double compat issue. Still, I think that a binding *can* provide a P2P-style bus by abusing endpoints with just a bit of convention rules. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source

Re: [systemd-devel] Compatibility between D-Bus and kdbus

understand the issue now. Given that and the fact that there are legitimate uses for AddMatch, I am in agreement that bindings need to provide the interception themselves. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel Open Source Technology Center