Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] bluez5_utils: Add config option to install "bdaddr"
Date: Wed, 15 Feb 2017 09:42:04 +0100	[thread overview]
Message-ID: <20170215094204.22df2cb5@free-electrons.com> (raw)
In-Reply-To: <20170215063911.ojfnao67fbpsojy7@tarshish>

Hello,

On Wed, 15 Feb 2017 08:39:11 +0200, Baruch Siach wrote:

> > How many tools are provided by bluez5_utils? If it's just a very small
> > set of tools, it's OK to have one option for each. But if there are
> > many small tools, we definitely don't want to have one option for each.  
> 
> The bluez5_utils-5.43 tools/ subdirectory has 56 executables, totaling 5.7MB. 
> Some are covered by covered by --enable-tools which we enable unconditionally, 
> some other are installed by --enable-experimental, and yet others are only 
> built by --enable-experimental. bdaddr falls in the last category.
> 
> > In any case, we need to provide a better guideline to Vishal, because
> > right now, we are not explaining how the patch should be fixed. If we
> > introduce something like BR2_PACKAGE_BLUEZ5_UTILS_TOOLS, then what
> > should be done with BR2_PACKAGE_BLUEZ5_UTILS_CLIENT or
> > BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL for example ?  
> 
> All should go under BR2_PACKAGE_BLUEZ5_UTILS_TOOLS, as well as --enable-tools, 
> IMO.

Well, 5.7 MB and 56 executables is definitely not a small amount, so I
would tend to instead accept a more fine-grained selection of the tools.

However, if indeed --enable-tools is optional, we shouldn't enable it
unconditional, but have an option for that.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-02-15  8:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 15:03 [Buildroot] [PATCH 1/1] bluez5_utils: Add config option to install "bdaddr" Vishal Thanki
2017-02-14 16:08 ` Baruch Siach
2017-02-14 20:14   ` Thomas Petazzoni
2017-02-15  6:39     ` Baruch Siach
2017-02-15  8:42       ` Thomas Petazzoni [this message]
2017-02-20 12:39         ` Vishal Thanki

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=20170215094204.22df2cb5@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox