Return-Path: <cyrus@holtmann.org>
Message-ID: <1337848490.15105.83.camel@aeonflux>
Subject: Re: [RFC] Reorganizing the BlueZ source tree
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Gustavo Padovan <gustavo@padovan.org>,
	linux-bluetooth@vger.kernel.org
Date: Thu, 24 May 2012 10:34:50 +0200
In-Reply-To: <CABBYNZLhWfS6Ff0S8SkCwSXxzt61NzNCBH-K78hQB6dtpPvJ6Q@mail.gmail.com>
References: <20120524081405.GA30941@joana>
	 <CABBYNZLhWfS6Ff0S8SkCwSXxzt61NzNCBH-K78hQB6dtpPvJ6Q@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Hi Luiz,

> > 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.

btio, gdbus, gobex and similar stay top-level. We are not going to
change that.

Regards

Marcel