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: Tue, 14 Feb 2017 21:14:43 +0100 [thread overview]
Message-ID: <20170214211443.00dc1a10@free-electrons.com> (raw)
In-Reply-To: <20170214160844.ts44yh2l4ghzwvad@tarshish>
Hello,
On Tue, 14 Feb 2017 18:08:44 +0200, Baruch Siach wrote:
> > +config BR2_PACKAGE_BLUEZ5_TOOLS_BDADDR
> > + bool "install bdaddr tool"
> > + depends on BR2_PACKAGE_BLUEZ5_UTILS_EXPERIMENTAL
> > + help
> > + The "bdaddr" tool is used for changing the Bluetooth device address.
>
> bdaddr is less than 100KB. I don't think it's worth another config option.
> 100KB is negligible when you already have glib and dbus. I'd suggested to
> either install bdaddr unconditionally, or have a single option for all tools/
> executables that are not covered by another config option already.
I would tend to agree, but we already have options like
BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL to install a single tool.
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.
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 ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-14 20:14 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 [this message]
2017-02-15 6:39 ` Baruch Siach
2017-02-15 8:42 ` Thomas Petazzoni
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=20170214211443.00dc1a10@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