that's really painful - especially if systemd-dbus is not going to keep abi...

On 11/01/2013 02:33 PM, Kyungmin Park wrote:

I think it's hard to be happened. Recent systemd activity they are migrate from libdbus to libsystemd-bus. And that's plan announced.

*From:*[email protected] [mailto:[email protected]] *On Behalf Of *Carsten Haitzler
*Sent:* Friday, November 01, 2013 2:26 PM
*To:* [email protected]
*Subject:* Re: [Dev] [RFC] kdbus transport for DBus

e_dbus and eldbus (the e one(s)) use libdbus - so if libdbus ports to kdbus.. efl will be fine. :)

On 11/01/2013 10:59 AM, HyungJun Choi wrote:

        On 2013-10-31, 17:50 -0700, Thiago Macieira wrote:

            the old protocol to the kdbus protocol. For us in Tizen, that mostly

    means

            porting ebus, libgio and QtDBus.

        typo of edbus?

        Anyone has some kind of summary about how many kind of D-Bus libs

        (libsystemd-bus, libdbus, edbus, libgio, QtDBus...) are used in Tizen

        and what their individual usage proportion etc.

    As far as I know, we are using libdbus, dbus-glib,dbus-python, edbus and

    gdbus) libraries on tizen2.x.

    As you know, the core library of the dbus-glib, dbus-python and edbus is

    libdbus.

    The core library of gdbus is libgio in glib.

    I checked the git repositories on tizen2.x and tizen3.

    Best Regards,

    Hyungjun.

    _______________________________________________

    Dev mailing list

    [email protected]  <mailto:[email protected]>

    https://lists.tizen.org/listinfo/dev



--
The above message is intended solely for the named addressee and may
contain trade secret, industrial technology or privileged and
confidential information otherwise protected under applicable law
including the Unfair Competition Prevention and Trade Secret Protection
Act. Any unauthorized dissemination, distribution, copying or use of the
information contained in this communication is strictly prohibited. If
you have received this communication in error, please notify the sender
by email and delete this communication immediately.

--
The above message is intended solely for the named addressee and may
contain trade secret, industrial technology or privileged and
confidential information otherwise protected under applicable law
including the Unfair Competition Prevention and Trade Secret Protection
Act. Any unauthorized dissemination, distribution, copying or use of the
information contained in this communication is strictly prohibited. If
you have received this communication in error, please notify the sender
by email and delete this communication immediately.

_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to