From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] utils/test-pkg: add option to enable NLS support
Date: Wed, 24 Jul 2019 00:13:59 +0200 [thread overview]
Message-ID: <20190724001359.0a290cf1@windsurf> (raw)
In-Reply-To: <20190723172336.24010-1-vadim4j@gmail.com>
Hello Vadim,
On Tue, 23 Jul 2019 20:23:36 +0300
Vadim Kochan <vadim4j@gmail.com> wrote:
> Sometimes the package or specific configuration should be build with and
> without NLS support which requires additionally append NLS related
> config options or to have separate config file or use additional shell
> script.
>
> So add helper command line option which appends config file with NLS
> options to the final config file which is now always stored in temporary
> file before merge it with the default configuration (even only -c was
> specified).
>
> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
Thanks for the patch. It seems like a good idea to test NLS-enabled
configurations in test-pkg indeed. However, I'm not sure it's a good
idea to make it conditional/optional. The idea of test-pkg is that
people run test-pkg, and it tells them if their new package seems to be
OK or not. Most people will not know which knobs/options to pass to
test-pkg to test all possible situations.
So I think we should instead ensure that test-pkg by default tests the
different combinations that we think are useful to test.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-07-23 22:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 17:23 [Buildroot] [PATCH 1/1] utils/test-pkg: add option to enable NLS support Vadim Kochan
2019-07-23 22:13 ` Thomas Petazzoni [this message]
2019-07-24 7:03 ` Vadim Kochan
2019-07-24 7:17 ` Thomas Petazzoni
2019-07-24 7:32 ` Vadim Kochan
2019-08-03 8:22 ` 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=20190724001359.0a290cf1@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