Return-Path: Message-ID: <1337852769.2115.47.camel@novo.hadess.net> Subject: Re: [RFC] Reorganizing the BlueZ source tree From: Bastien Nocera To: Luiz Augusto von Dentz Cc: Gustavo Padovan , linux-bluetooth@vger.kernel.org Date: Thu, 24 May 2012 10:46:09 +0100 In-Reply-To: References: <20120524081405.GA30941@joana> Content-Type: text/plain; charset="ISO-8859-1" Mime-Version: 1.0 Sender: linux-bluetooth-owner@vger.kernel.org List-ID: On Thu, 2012-05-24 at 11:20 +0300, Luiz Augusto von Dentz wrote: > Hi Gustavo, > > On Thu, May 24, 2012 at 11:14 AM, Gustavo Padovan wrote: > > Hi Everyone, > > > > The last profiles addition to BlueZ increased a lot the number of folders we > > have in the root dir of the project and it looks like more profiles (and more > > folders) are expected to come. > > > > I talked a bit with Johan about changing the hierarchy of the BlueZ tree and > > the following proposal where 2 new folders are created, 'profiles' and 'libs' > > and things are moved to them. > > > > compat -> /dev/null (will be removed on 5.0) > > alert -> profiles > > audio -> profiles > > cups -> profiles > > deviceinfo -> profiles > > health -> profiles > > input -> profiles > > lib -> profiles > > network -> profiles > > proximity -> profiles > > sap -> profiles > > serial -> profiles > > thermometer -> profiles > > time -> profiles > > btio -> libs > > gdbus -> libs > > sbc -> libs > > emulator -> tools > > mgmt -> tools > > monitor -> tools > > attrib > > doc > > plugins > > scripts > > src > > test > > tools > > unit > > Sounds good, the only problem are gdbus and btio, if we merge obexd > into BlueZ btio will no longer be shared but for gdbus we would have > to align with other projects as well. While you're at it, change gdbus' name to something that doesn't clash with the GIO GDBus.