Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mikko Rapeli <mikko.rapeli@bmw.de>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] busybox: enable unicode support
Date: Wed, 17 Jul 2019 12:44:54 +0100	[thread overview]
Message-ID: <a098852b41fcdb4adcda5060a3fd87694391e0ea.camel@linuxfoundation.org> (raw)
In-Reply-To: <1563354517-31850-1-git-send-email-mikko.rapeli@bmw.de>

On Wed, 2019-07-17 at 12:08 +0300, Mikko Rapeli wrote:
> While creating and deleting files with unicode or other
> encodings works, it's annoying when ls and other core utils
> show questionmarks instead of the unicode characters.
> In 2019, it's quite common that users of embedded devices
> based on yocto need unicode support. Debugging a box with
> unicode encoded file names is a bit annoying when core utils
> from busybox don't support them.
> 
> The unicode config fragment has the same config as Debian in their
> deb and udeb builds of version 1:1.30.1-4.
> 
> If developers do not want this or other default yocto features in
> busybox,
> or optimize the configuration for size, then they likely run a
> completely
> custom configuration. Thus I think it's safe to enable unicode
> support
> by default.
> 
> Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de>
> ---
>  meta/recipes-core/busybox/busybox/unicode.cfg | 10 ++++++++++
>  meta/recipes-core/busybox/busybox_1.31.0.bb   |  1 +
>  2 files changed, 11 insertions(+)
>  create mode 100644 meta/recipes-core/busybox/busybox/unicode.cfg

Can you give an idea of the size implications of this change?

Cheers,

Richard



  parent reply	other threads:[~2019-07-17 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17  9:08 [PATCH 1/2] busybox: enable unicode support Mikko Rapeli
2019-07-17  9:08 ` [PATCH 2/2] cve-check.bbclass: initialize to_append Mikko Rapeli
2019-07-17 11:44 ` Richard Purdie [this message]
2019-07-17 12:24   ` [PATCH 1/2] busybox: enable unicode support Mikko.Rapeli
2019-07-17 13:26     ` Burton, Ross
2019-07-20  2:31     ` Khem Raj

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=a098852b41fcdb4adcda5060a3fd87694391e0ea.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=mikko.rapeli@bmw.de \
    --cc=openembedded-core@lists.openembedded.org \
    /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