From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 0/2] Add gettext-tiny package
Date: Sun, 10 Mar 2019 10:11:26 +0100 [thread overview]
Message-ID: <20190310101126.3d738624@windsurf> (raw)
In-Reply-To: <20190310002005.jglt6ptlgctyz6eb@vkochan-ThinkPad-T470p>
Hello Vadim,
On Sun, 10 Mar 2019 02:20:05 +0200
Vadim Kochan <vadim4j@gmail.com> wrote:
> Many thanks for your feedback! Using the gnu gettext's tar is really better
> idea! Regarding ecryptfs-utils - yes, I think the patch might be really easy,
> something like this:
>
> ...
> function trans {
> if command -v gettext &> /dev/null; then
> gettext @
> else
> echo @
> fi
> }
> ...
>
> and replace gettext -> trans in scripts.
Sounds good! Will you work on this ?
So, we agree that for the target gettext, only gettext-gnu will be a
provider when BR2_SYSTEM_ENABLE_NLS=y. When BR2_SYSTEM_ENABLE_NLS is
disabled, we don't have any target gettext package. Correct ? If so,
then I'll rework my branch to take this into account.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-10 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 21:55 [Buildroot] [PATCH v3 0/2] Add gettext-tiny package Vadim Kochan
2019-02-12 21:55 ` [Buildroot] [PATCH v3 1/2] package/gettext: Turn into virtual package Vadim Kochan
2019-02-12 21:55 ` [Buildroot] [PATCH v3 2/2] package/gettext-tiny: Add new package Vadim Kochan
2019-03-09 22:37 ` [Buildroot] [PATCH v3 0/2] Add gettext-tiny package Thomas Petazzoni
2019-03-10 0:20 ` Vadim Kochan
2019-03-10 9:11 ` Thomas Petazzoni [this message]
2019-03-10 10:18 ` Yann E. MORIN
2019-03-10 23:05 ` Vadim Kochan
2019-03-11 8:02 ` Thomas Petazzoni
2019-03-11 10:46 ` Vadym Kochan
2019-03-11 8:01 ` 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=20190310101126.3d738624@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.