Return-Path: Message-ID: <1339152010.19312.32.camel@novo.hadess.net> Subject: Re: [RFC] Reorganizing the BlueZ source tree From: Bastien Nocera To: Luiz Augusto von Dentz Cc: Marcel Holtmann , Gustavo Padovan , linux-bluetooth@vger.kernel.org Date: Fri, 08 Jun 2012 11:40:10 +0100 In-Reply-To: References: <20120524081405.GA30941@joana> <1337852769.2115.47.camel@novo.hadess.net> <1337853929.15105.84.camel@aeonflux> <1338998206.19312.10.camel@novo.hadess.net> <1339023575.1817.114.camel@aeonflux> <1339148670.19312.23.camel@novo.hadess.net> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 List-ID: 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 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.