All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Kochan <vadim4j@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/gettext: Turn into virtual package
Date: Thu, 3 Jan 2019 16:28:52 +0200	[thread overview]
Message-ID: <CAMw6YJKfY_+pK=gDCb9QF=sbg+RXhJbgC=zJC8qXy_MxMwjsVg@mail.gmail.com> (raw)
In-Reply-To: <20181231160614.0f7e9f0b@windsurf>

Hi Thomas, All

On Mon, Dec 31, 2018 at 5:06 PM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello Vadim,
>
> On Mon, 31 Dec 2018 06:03:30 +0200, Vadim Kochan wrote:
>
> > > I'm not convinced by how this virtual package is handled in Config.in.
> > > In fact, if you apply both of your patches, it's broken, you have:
> > >
> > > config BR2_PACKAGE_PROVIDES_HOST_GETTEXT
> > >         string
> > >         default "host-gettext-gnu" if BR2_PACKAGE_GETTEXT_GNU
> > >         default "host-gettext-tiny" if BR2_PACKAGE_GETTEXT_TINY
> > >
> > So looks like it needs to be enabled by default "host-gettext-gnu" but should
> > allow to set "host-gettext-tiny" if BR2_PACKAGE_GETTEXT_TINY was forced
> > by the user ?
>
> No, I don't think that's what we want. Is there any reason to use
> host-gettext-gnu, unless BR2_SYSTEM_ENABLE_NLS is enabled ?
>
> If not, then I think we should:
>
>         default "host-gettext-gnu" if BR2_SYSTEM_ENABLE_NLS
>         default "host-gettext-tiny" if !BR2_SYSTEM_ENABLE_NLS
>
> > May be I don;t have a view of a whole picture, but for me it looks simple -
> > by default gettext-gnu is selected when ENABLE_NLS is set, but
> > gettext-tiny should
> > be selected by force choosing the BR2_PACKAGE_GETTEXT_TINY
>
> We don't need BR2_PACKAGE_GETTEXT_TINY at all. Just make the virtual
> package behave properly, using gettext-gnu as the provider when
> BR2_SYSTEM_ENABLE_NLS=y, and using gettext-tiny as the provider when
> BR2_SYSTEM_ENABLE_NLS is not enabled.
>
> >. For the "host"
> > case - the similar case with the only difference that "tiny" might be
> > selected if NLS is disabled.
>
> Why would one want to use the full gettext when NLS is disabled ? When
> NLS is disabled, you don't care about message translations, so the
> dummy implementation provided by gettext-tiny should be enough.
>
> However: this is a massive change in Buildroot. Most people are
> building with BR2_SYSTEM_ENABLE_NLS disabled (that's our default), so
> such a change will mean that everybody will switch from one day to the
> other from gettext-gnu to gettext-tiny.
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com

Why do we need default host-gettext dependencies for such packages
like wine, flex
if they builds successfully (I tried uclibc, musl) if to manually
remove such dependency
from their *.mk files ?

Regards,
Vadim Kochan

  reply	other threads:[~2019-01-03 14:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-23 15:04 [Buildroot] [PATCH 0/2] Add gettext-tiny package Vadim Kochan
2018-12-23 15:04 ` [Buildroot] [PATCH 1/2] package/gettext: Turn into virtual package Vadim Kochan
2018-12-23 15:36   ` Yann E. MORIN
2018-12-30 17:10   ` Thomas Petazzoni
2018-12-31  4:03     ` Vadim Kochan
2018-12-31 15:06       ` Thomas Petazzoni
2019-01-03 14:28         ` Vadim Kochan [this message]
2019-01-03 14:28           ` Thomas Petazzoni
     [not found]             ` <CAMw6YJ+xU9GiZ809dCQTmPEgtpu3iCOErT5w7fqoee09R-hpaQ@mail.gmail.com>
     [not found]               ` <CAMw6YJLvioTwKbgAdYvtZqbVg1W-RAADT_umZkGMaw9MnVpHMw@mail.gmail.com>
2019-01-04  8:39                 ` Thomas Petazzoni
2018-12-23 15:04 ` [Buildroot] [PATCH 2/2] package/gettext-tiny: Add new package Vadim Kochan
2018-12-23 21:21   ` Yann E. MORIN
2018-12-31  4:07     ` Vadim Kochan

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='CAMw6YJKfY_+pK=gDCb9QF=sbg+RXhJbgC=zJC8qXy_MxMwjsVg@mail.gmail.com' \
    --to=vadim4j@gmail.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.