All of lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [RFC] Reorganizing the BlueZ source tree
Date: Thu, 24 May 2012 10:34:50 +0200	[thread overview]
Message-ID: <1337848490.15105.83.camel@aeonflux> (raw)
In-Reply-To: <CABBYNZLhWfS6Ff0S8SkCwSXxzt61NzNCBH-K78hQB6dtpPvJ6Q@mail.gmail.com>

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



  reply	other threads:[~2012-05-24  8:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24  8:14 [RFC] Reorganizing the BlueZ source tree Gustavo Padovan
2012-05-24  8:20 ` Luiz Augusto von Dentz
2012-05-24  8:34   ` Marcel Holtmann [this message]
2012-05-25 19:40     ` Lucas De Marchi
2012-05-24  9:46   ` Bastien Nocera
2012-05-24 10:05     ` Marcel Holtmann
2012-06-06 15:56       ` Bastien Nocera
2012-06-06 22:59         ` Marcel Holtmann
2012-06-08  9:44           ` Bastien Nocera
2012-06-08 10:02             ` Luiz Augusto von Dentz
2012-06-08 10:40               ` Bastien Nocera
2012-06-08 11:46                 ` Marcel Holtmann
2012-06-08 11:59                   ` Bastien Nocera
2012-06-08 12:07                     ` Marcel Holtmann
2012-06-08 12:27                       ` Bastien Nocera
2012-05-24  8:23 ` Johan Hedberg
2012-05-24  8:27   ` Gustavo Padovan
2012-05-25 14:41 ` Joao Paulo Rechi Vita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1337848490.15105.83.camel@aeonflux \
    --to=marcel@holtmann.org \
    --cc=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.