Re: [RFC] Reorganizing the BlueZ source tree

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

 



On Fri, 2012-06-08 at 13:02 +0300, Luiz Augusto von Dentz wrote:
> Hi Bastien
> 
> On Fri, Jun 8, 2012 at 12:44 PM, Bastien Nocera <hadess@xxxxxxxxxx> wrote:
> > On Thu, 2012-06-07 at 07:59 +0900, Marcel Holtmann wrote:
> >>
> >> and I still have all the rights to do so.
> >>
> >> As long as we are still based on GLib, this will stay as it is. I am
> >> not
> >> jumping through any hoops, because David wouldn't respect prior art.
> >
> > How exactly would would have called a D-Bus implementation in GLib?
> 
> Well you could have called godbus as that is more a gobject binding
> than a pure glib/GMainLoop one.

GLib lives in a single tarball. It's only Marcel's hate for GObject and
the apparent need to be able to replace glib that spawned this thin
wrapper on top of libdbus you're using now.

GLib's APIs don't differentiate which shared library they come from.

--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux