public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "Valek, Andrej" <andrej.valek@siemens.com>,
	"armccurdy@gmail.com" <armccurdy@gmail.com>,
	"steve@sakoman.com" <steve@sakoman.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	"raj.khem@gmail.com" <raj.khem@gmail.com>
Subject: Re: [OE-core][PATCH] vim: add option to disable NLS support
Date: Thu, 26 Aug 2021 13:00:46 +0100	[thread overview]
Message-ID: <b2dab4ebd32e02a84bc7087a3e3ac62c78255547.camel@linuxfoundation.org> (raw)
In-Reply-To: <98ece42c21301b8384d4b2e92cedb232b324b6a0.camel@siemens.com>

On Thu, 2021-08-26 at 11:24 +0000, Valek, Andrej wrote:
> Hello Richard,
> 
> If it isn't a big deal, I can use the "--enable" variant. If we keep --
> enable-nls like a default, we will brake nothing I guess. (It's enabled
> by default anyway). So I'm adding there only a feature to disable it
> with PACKAGEOPTION.

Yes, lets use --enable please since that is the way the rest of the world/code 
works.

I'm a bit worried about the nls option since the recipe does have BBCLASSEXTEND
for native/nativesdk and we do disable nls for native by default. As you say,
the patch probably doesn't change anything but it is a bit of an oddity.

The code does look to be using gettext and there is a gettext-native dependency
but the recipe does not use the gettext class. Why? Not sure.

I'll put the patch in for testing if we can use the standard format though
(which should work since I checked and configure is using the standard autoconf
macros).

Cheers,

Richard


  reply	other threads:[~2021-08-26 12:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 10:12 [OE-core][PATCH] vim: add option to disable NLS support Andrej Valek
2021-08-23 11:23 ` [OE-core][PATCH v2] busybox: 1.33.1 -> 1.34.0 Andrej Valek
2021-08-23 16:12 ` [OE-core][PATCH] vim: add option to disable NLS support Khem Raj
2021-08-23 17:12   ` Andrej Valek
2021-08-23 22:14     ` Andre McCurdy
2021-08-24  6:56       ` Andrej Valek
2021-08-26  9:58         ` Andrej Valek
2021-08-26 10:59           ` Richard Purdie
2021-08-26 11:24             ` Andrej Valek
2021-08-26 12:00               ` Richard Purdie [this message]
2021-08-26 13:15 ` [OE-core][PATCH v2] " Andrej Valek
2021-09-01 19:04   ` Andrej Valek
2021-09-01 22:35     ` Steve Sakoman
2021-09-08  7:49       ` Andrej Valek
2021-09-08 14:26         ` Steve Sakoman

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=b2dab4ebd32e02a84bc7087a3e3ac62c78255547.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=andrej.valek@siemens.com \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=steve@sakoman.com \
    /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