From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/2] add gettext-tiny package
Date: Sun, 31 Mar 2019 14:30:00 +0200 [thread overview]
Message-ID: <20190331143000.5ed20d14@windsurf> (raw)
In-Reply-To: <20190331142907.5b459037@windsurf>
Hello,
On Sun, 31 Mar 2019 14:29:07 +0200
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> A couple of notes/suggestions:
>
> - It would be nice if you could work with upstream gettext-tiny to
> make sure gettext-tiny provides everything we need, without the need
> to bring some files from gettext-gnu.
>
> - The ecryptfs-utils package can probably see its BR2_USE_WCHAR
> dependency removed. Indeed, when BR2_SYSTEM_ENABLE_NLS is disabled,
> we use gettext-tiny, and wchar is no longer needed. And
> BR2_SYSTEM_ENABLE_NLS depends on wchar.
>
> - I have sent a patch for utils/genrandconfig that randomly sets BR2_SYSTEM_ENABLE_NLS=y in the autobuilder configurations, in order to test this situation.
Gah, I hit Ctrl+Enter and it sent the e-mail before I finished. I meant
to wrap this line, and say:
Thanks a lot for this contribution, it was not trivial, but it's
definitely a nice improvement!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-03-31 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 23:08 [Buildroot] [PATCH v4 0/2] add gettext-tiny package Vadim Kochan
2019-03-27 23:08 ` [Buildroot] [PATCH v4 1/2] package/gettext: turn into virtual package Vadim Kochan
2019-03-27 23:08 ` [Buildroot] [PATCH v4 2/2] package/gettext-tiny: new package Vadim Kochan
2019-03-31 12:29 ` [Buildroot] [PATCH v4 0/2] add gettext-tiny package Thomas Petazzoni
2019-03-31 12:30 ` Thomas Petazzoni [this message]
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=20190331143000.5ed20d14@windsurf \
--to=thomas.petazzoni@bootlin.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