From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/bluez5_utils: needs readline
Date: Wed, 17 Jan 2018 22:23:11 +0100 [thread overview]
Message-ID: <ver4jexs69.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20180114053204.qzh6l3xgqywgcmyr@sapphire.tkos.co.il
Am Sun, 14 Jan 2018 07:32:04 +0200 schrieb Baruch Siach:
> Hi Bernd,
>
> On Sat, Jan 13, 2018 at 11:45:32PM +0100, Bernd Kuhls wrote:
[...]
>> + select BR2_PACKAGE_READLINE
>
> I don't think that this is the correct fix. The bluez README file says:
>
> --disable-client
>
> Disable support for the command line client
>
> By default the command line client is enabled and uses
> the readline library. For specific systems where BlueZ
> is configured by other means, the command line client
> can be disabled and the dependency on readline is
> removed.
>
> So this does not look like a decision to make readline a mandatory
> dependency,
> but a bug that needs to be fixed upstream.
Hi Baruch,
this commit https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?
id=70b8b754f8e6f9abe9211c686b279dbef16bf666
"client: Make use of bt_shell.
Use bt_shell instead of readline directly."
removed readline code from client code and replaced it with calls to
bt_shell, bt_shell itself is not used exclusively by client code anymore,
see the commit I mentioned in my patch ( https://git.kernel.org/pub/scm/
bluetooth/bluez.git/commit/?id=bee3796113196da1b3f56da42fcae4d9bae6695e )
and the many source code files which include "src/shared/shell.h".
Afaics this does look like an outdated README file and not a bug in the
source code, what do you think? Before writing to the bluez devs I would
like to reach a consensus about what to ask them ;)
Regards, Bernd
next prev parent reply other threads:[~2018-01-17 21:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 22:45 [Buildroot] [PATCH 1/1] package/bluez5_utils: needs readline Bernd Kuhls
2018-01-14 5:32 ` Baruch Siach
2018-01-14 13:53 ` Thomas Petazzoni
2018-01-17 8:43 ` Thomas Petazzoni
2018-01-17 21:23 ` Bernd Kuhls [this message]
2018-01-18 4:40 ` Baruch Siach
2018-03-02 20:59 ` Jörg Krause
2018-04-20 10:20 ` Thomas Petazzoni
2018-04-20 14:08 ` Thomas Petazzoni
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=ver4jexs69.ln2@ID-313208.user.individual.net \
--to=bernd.kuhls@t-online.de \
--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